000035408 - RSA Adaptive Authentication (On Premise) customer looking to unbind devices of end users.

Document created by RSA Customer Support Employee on Aug 10, 2017
Version 1Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000035408
Applies ToRSA Product Set: Adaptive Authentication (OnPrem)
RSA Product/Service Type: Adaptive Authentication (OnPrem)
RSA Version/Condition: 7.x
 
IssueA customer was looking to clean up some of the bound devices of their end-users and asked if they could go into the database and simply set the delete_flag column to true.
 
TasksRSA does not recommend make direct changes to the database, as there may be dependencies that are not apparent, and could lead to further issues.
ResolutionIt is possible to run the following Soap request to unbind all devices of a specified user:
 
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <updateUser xmlns="http://ws.csd.rsa.com">
         <request>
            <identificationData>
               <userName>${#TestSuite#username}</userName>
               <userStatus>VERIFIED</userStatus>
               <userType>PERSISTENT</userType>
            </identificationData>
            <messageHeader>
               <apiType>DIRECT_SOAP_API</apiType>
               <requestType>UPDATEUSER</requestType>
               <version>7.0</version>
            </messageHeader>
            <securityHeader>
               <callerCredential>${#TestSuite#callerCredential}</callerCredential>
               <callerId>${#TestSuite#callerId}</callerId>
               <method>PASSWORD</method>
            </securityHeader>
            <deviceManagementRequest>
               <actionTypeList>
                  <deviceActionTypes>UNBIND_ALL_DEVICES</deviceActionTypes>
               </actionTypeList>
            </deviceManagementRequest>
            <runRiskType>NONE</runRiskType>
         </request>
      </updateUser>
   </soap:Body>
</soap:Envelope>


The end-user will like be challenged the next time they log in.
 

Attachments

    Outcomes