This requires the SOAP response as a parameter. GetResponseFirstPairs ( response ) ¶ Description: Gets the 1st level of important main response fields from the VIP SOAP call and tells what fields are accessibleįirstPair ( string) – The first pair in the tuple field GetPreviousResponseValue ( firstPair ) ¶ Description: List – Containing all the first pair values of each tuple This will not work if there was no previous call in the client. Gets the 1st level of important main response fields from previous VIP SOAP call and tells what fields are accessible GetPreviousResponseFirstPairs ( ) ¶ Description: GetFieldContent ( fieldname ) ¶ Description: forcePinChange ( boolean) – Force the PIN to expire after first use.ĭeleteUser ( requestId, userId, onBehalfOfAccountId=None ) ¶ Description:ĭelete/remove a user from VIP User Servicesĭeleting a user is a cascading operation: when deleted, all credentials associated with user are removed and if credential is not associated with any other user, it is also deactivated.4 to 128 characters max, depending on PIN policy restrictions. pin ( string) – Optional user PIN for 1st factor authentication.If the user attempts to use a PIN that has already been cleared, or has not been enabled by the user PIN policy, VIP User Services will return an error.ĬreateUser ( requestId, userId, onBehalfOfAccountId=None, pin=None, forcePinChange=None ) ¶ Description:īy default users are created as Enabled. If the user attempts to use a temporary security that has been cleared, an error will be returned from VIP User Services stating security code is not set.ĬlearUserPin ( requestId, userId, onBehalfOfAccountId=None ) ¶ Description: Removes a temporary security code from a user trustedDevice ( boolean) – Allows the device to be remembered in the credential for future easy usageĬlearTemporaryPassword ( requestId, userId, onBehalfOfAccountId=None ) ¶ Description:.MANDATORY - SMS, voice, and system-generated credentials need to be registered first The parent account uses its own certificate to authenticate the request to VIP User Services.ĪddCredentialTrustedDevice ( requestId, userId, credentialId, credentialType, trustedDevice, friendlyName=None, trustedCredentialDevice=None, onBehalfOfAccountId=None ) ¶ Description:Īssigns a credential to a user in VIP User Services by setting the device to be remembered onBehalfOfAccountId ( string) – The parent account that this request is done on behalf of a child account.trustedCredentialDevice ( boolean) – Allows the device to be remembered in the credential for future easy usage.friendlyName ( string) – A user-defined name to identify the credential.otp2 ( string) – The second one time security code that is generated by the user’s credential. otp1 ( string) – The first one time security code that is generated by the user’s credential.credentialType ( string) – Identifies the credential type: STANDARD_OTP (hardware or software VIP credential, including VIP Access for mobile), CERTIFICATE, SMS_OTP, VOICE_OTP, SERVICE_OTP.credentialId ( string) – Unique identifier of the credential.userId ( string) – Unique user ID (i.e.- email address, login name).requestId ( string) – A unique identifier of the request for the enterprise application.MANDATORY - SMS, voice, and system-generated credentials need to be registered first Also, you have choice of setting the binding status to Enabled or Disabled upon adding credential to user. addCredentialOtp ( requestId, userId, credentialId, credentialType, otp1, otp2=None, friendlyName=None, trustedCredentialDevice=None, onBehalfOfAccountId=None ) ¶ Description:Īssigns a credential to a user in VIP User Services using one time password(s) Reference HTTPHandler for further information on how to setup the client.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |