000011958 - Session ID error after calling update request

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000011958
Applies To The updateUser method updates the user?s profile, including any Site-to-User and credential information.The authenticate method verifies a user using one or more credentials. 

You can update the binding type to NONE or HARD_BIND.HARD_BIND indicates the device token is bound to the user?s device.

Authenticate call is placed to a authenticate the users. Once successful the response would be as SUCCESS. Now a request to bind the device can be sent through the update user SOAP call to HARD_BIND the device.

The authenticate response does not return any session ID .

A session  is no longer valid after a  successful authenticate.

If you are going to send a separate bind request there is no need to supply a sessionid.So in order to avoid such error it is suggested to remove the session id from the SOAP request.
IssueError occurs  on the HARD bind update user call when a valid session ID is passed based on the response form the authenticate call.
Legacy Article IDa45486

Attachments

    Outcomes