Status Request Response
Status Request Response

Status Request Response

The Profile Client sends this intent in response to a status request (Profile Client originated) from the third-party application.

Prerequisites

  • The Profile Client has received the
    com.zebra.dfs.ACTION_LOGIN_STATUS
    intent.
  • The minimum required Profile Client Android version is 2.0.21200.

Intent Definition

Name
Description
Action
com.zebra.dfs. ACTION_LOGIN_STATUS_RESPONSE
Intent Type
broadcast
Extra 0
This extra specifies
login_info_status_response
  information necessary to query the client’s login status. See the payload definition below. This extra may or may not be encrypted.
Extra 0 - sent unencrypted
This extra specifies
login_info_status_response
when not encrypted. This is an optional parameter.
                         Type
String
                         Name
login_info_status_response
                         Value
String in JSON format
Extra 0 – sent encrypted
This extra specifies
login_info_status_response
when encrypted. This is an optional parameter.
                         Type
Byte array
                         Name
login_info_status_response
                         Value
See code snippet under Encryption/Decryption

ADB Example

login_info_status_response Payload

The
login_info_status_response
parameter contains JSON formatted data with the following fields:
{ "user_name": "username", //mandatory "request_id": <unique_number>, //mandatory "status" : "<user_login_status>" //mandatory - LOGGED_IN, LOGGED_OUT or // ERROR_MISMATCH_USERNAME }
  • LOGGED_IN
    indicates that the Profile Client is logged in. It does not indicate that a role is selected, or that the WFC Voice and/or PTT Pro Clients are logged in.
  • ERROR_MISMATCH_USERNAME
    is returned when the
    user_name
    from
    login_info_status
    does not match with the current logged in user by ignoring the upper/lower case and domain name.
  • The Profile Client encrypts the
    login_info_status_response
    payload if the client is configured with a
    secret_key
    . Otherwise, it is sent in the clear. Even if the
    login_info_status
    is sent in the clear,
    login_info_status_response
    is encrypted and sent if the
    secret_key
    has been configured.