Listing Associations

RiskMinder Web Services Developer's Guide › Performing Risk Evaluation and Managing Associations › Listing Associations

Listing Associations

RiskMinder uniquely identifies a user as a valid user of your system by automatically associating (or binding) a user to the device that they use to access your application. This is referred to as an association (or device binding) in RiskMinder terminology. Users who are not bound are more likely to be challenged in order to be authenticated.

RiskMinder also allows users to be bound to more than one device. For example, a user can use a work computer and a home computer to access your application. Similarly, you can bind a single device to more than one user. For example, members of a family can use one computer to access your application.

Important! It is recommended that you discourage users from creating associations with publicly shared devices, such as systems in an Internet cafe or kiosk.

This section walks you through the following tasks for listing stored user-device associations for a specified user:

Preparing the Request Message
Invoking the Web Service
Interpreting the Response Message

Preparing the Request Message

You must use the listAssociationsRequest message to view all known associations for the specified user. The following table lists the elements of this request message.

Element	Mandatory	Description

callerId	No	Unique transaction identifier that your calling application can include. This identifier helps in tracking related transactions.
User Context Elements
userContext	No	The user details, as described by orgName and userName.
userContext/ orgName	No	The name of the organization to which the end user belongs.
userContext/ userName	Yes	The name of the user who performed the transaction.
Administration Context Type Elements
adminContextType	No	The administrator details, as described by orgName, adminName, and locale, who initiated the Web service call.
adminContextType/ orgName	No	The name of the organization to which the administrator who initiated the Web service call belongs.
adminContextType/ adminName	No	The name of the administrator who initiated the Web service call.
adminContextType/ locale	No	The locale used by the administrator. The output message is converted to this locale.
Additional Input Elements
additionalInput	No	Enables you to set additional inputs if you want to augment RiskMinder’s risk evaluation capability by specifying additional information. In such cases, you need to set the extra information in name-value pairs. name: The name with which you want to create the key pair. value: The corresponding value for name. Note: You can add more than one of these elements.

Invoking the Web Service

To list all the stored associations for a specified user:

(Optional) Include the authentication and authorization details in the header of the listAssociations operation. See "Managing Web Services Security" for more information on the header elements.
Use the listAssociationsRequest elements to set the required information, as listed in the table.
Use the listAssociationsRequest message and construct the input message by using the details specified in preceding step.
Invoke the listAssociations operation of the RiskFortEvaluateRiskSvc service to list all associations for the given user.
This operation returns the listAssociationsResponse message that includes the association details and the success result. See the following section for more information on the response message.

Interpreting the Response Message

The response message, listAssociationsResponse, returns the list and details of all known associations for the specified user in the SOAP envelope header. These elements are explained in the following table. The SOAP body returns a success message if the operation was performed successfully. If there are any errors, then the riskfortFault response is returned. See appendix, "Exceptions and Error Codes" for more information on the SOAP error messages.

Element	Description

Association Elements
associationName	The name(s) of device association(s) found for the specified user.
creationDate	The date and time when the association was created.
deviceID	The corresponding Device ID(s) extracted from the Device ID store on the end user's computer.
status	The status of the association: 1: Indicates that the association is valid and active. 0: Indicates that the association is not valid any more and has been deleted.
RiskFort Success Elements
successMessage	Contains the string that indicates whether the operation was successful or not.
transactionID	The unique transaction identifier.