Fetching User Attributes

RiskMinder Web Services Developer's Guide › Managing Users and Accounts › Authenticating LDAP Users › Using Directory Service Attributes › Fetching User Attributes

Fetching User Attributes

The attributes that are used to store the user information in the directory service can be read using the getQnAAttributes operation. This section walks you through the following steps related to this operation:

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

Preparing the Request Message

The following table lists the elements of the QnAAttributesRequest message.

Element	Mandatory	Description
orgName	Yes	The name of the LDAP organization to which the user attributes that you want to fetch belong.
clientTxId	No	The unique transaction identifier that your calling application can include. This identifier helps in tracking the related transactions.

Invoking the Web Service

To fetch the user attributes:

(Optional) Include the authentication and authorization details in the header of the getQnAAttributes operation. See "Managing Web Services Security" for more information on the header elements.
Use the getQnAAttributesRequest elements to collect the organization information, as listed in the table.
Use the QnAAttributesRequest message and construct the input message by using the details specified in the preceding step.
Invoke the getQnAAttributes operation of the ArcorUserRegistrySvc service to fetch the user attributes of the LDAP organization.
This operation returns the QnAAttributesResponse message that includes the transaction identifier, authentication token, and user attributes. See the following section for more information on the response message.

Interpreting the Response Message

The response message, QnAAttributesResponse, returns the transaction identifier and the authentication token in the SOAP envelope header. The SOAP body includes the user attributes for a successful transaction and the Fault response for an error condition.

See the following table for more information on the elements returned for a successful transaction. Refer to appendix, "Exceptions and Error Codes" if there are any errors.

Element	Description

Header Elements
udsTransactionID	The unique identifier of the transaction performed by using UDS.
authToken	The authentication token that is returned if the credential verification to access the Web service was successful. This token eliminates the need for you to present the authentication credential for successive access to the Web service. By default, the authentication token by default is valid for one day, after which you need to authenticate again.
Body Elements
The user attributes configured in the LDAP.