authenticateUserWithPush request
The authenticateUserWithPush request authenticates users through a push notification.
Send the request to: https://userservices-auth.vip.symantec.com/vipuserservices/AuthenticationService_1_10
authenticateUserWithPush
input fields provides details about the authenticateUserWithPush
input fields. Input Field | Required? | Type | Purpose |
|---|---|---|---|
requestId | Y | string | A unique identifier of the request for the enterprise application. The request ID accepts from 4 to 40 alphanumeric characters and underscores. This identifier may be useful for troubleshooting purposes. |
userId | Y | string | Unique ID for the user (for example, the user email address, the user’s logon name, or a unique ID that maps to user’s logon name). The user ID accepts 1 to 128 international characters. The user ID is not case-sensitive in look-up operations. |
pin | N | string | Optional user PIN for first-factor authentication. The PIN may be 4 to 128 international characters in length, depending on restrictions of the PIN policy. |
pushAuthData :displayParameters | N | list | Passes and displays content to users in the push notification. You can customize display messages up to 250 characters. However, some phones may not display complete messages. The following keys are currently supported: This input field contains parameters that define the push notification that is sent to the user’s push-capable mobile device.
|
pushAuthData :requestParameters | N | list | The following keys are currently supported:
|
authContext | N | string | A map containing the parameters that control how the authentication is performed. VIP User Services accepts an authentication level for the authContext field. The authentication level defines the authentication methods that VIP User Services can validate against. If an authentication level is sent, the push notification is validated only if the authentication level allows Mobile Push. This level must match an authentication level configured in VIP Manager.
|