Previous Topic: Listing AssociationsNext Topic: Performing Selected Administration Tasks


Deleting Associations

RiskMinder also enables you to delete user-device associations. However internally, RiskMinder does not remove the association entry. It merely sets this value to 0 for the given association.

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

Preparing the Request Message

You must use the deleteAssociationRequest message to delete the specified associations for a 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.

Association Element

associationName

Yes

The name of the association that you want to delete.

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 delete the listed associations for a specified user:

  1. (Optional) Include the authentication and authorization details in the header of the deleteAssociation operation. See "Managing Web Services Security" for more information on the header elements.
  2. Use the deleteAssociationRequest elements to set the required information, as listed in the table.
  3. Use the deleteAssociationRequest message and construct the input message by using the details specified in preceding step.
  4. Invoke the deleteAssociation operation of the RiskFortEvaluateRiskSvc service to delete an association.

    This operation returns the deleteAssociationResponse message that includes the details about deleted association(s) and the success result. See the following section for more information on the response message.

Interpreting the Response Message

The response message, deleteAssociationResponse, returns the list and details of all deleted 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 of device association that was deleted 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 device.

status

The status of the association:

  • 0: Indicates that the association is not valid any more and has been deleted.
  • 1: Indicates that the association is valid and active.

RiskFort Success Elements

successMessage

Contains the string that indicates whether the operation was successful or not.

transactionID

The unique identifier of the transaction.