Fetching Directory Service Attributes

CA AuthMinder Web Services Guide › Managing Organizations › Fetching Directory Service Attributes

Fetching Directory Service Attributes

The listRepositoryAttributes operation is used to fetch the directory service user attributes that are mapped to AuthMinder-supported user attributes.

This section walks you through the following topics for fetching the user attributes that the directory service supports:

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

Preparing the Request Message

The listRepositoryAttributesRequest message is used to fetch directory service user attributes that are mapped to AuthMinder-supported user attributes. The following table lists the elements of this request message:

Element	Mandatory	Description
repositoryType	Yes	The directory service where the user information resides. Possible values are: ARUSER: For organizations that are created in the AuthMinder database. LDAP: For organizations that are mapped with LDAP repository.
ldapDetails	No	The details of the directory service where the user information is available. See "ldapDetails" in the table containing information about the createOrgRequest message.
connectionCredential	No	The information required to connect to the directory service. See "connectionCredential" in the table containing information about the createOrgRequest message.
redirectSearchSchema	No	The schema that has to be used to search for the values whose attributes are in a different node.
redirectSearchAttribute	No	The value of the attribute that has to be searched in the redirectSearchSchema.
clientTxId	No	Unique transaction identifier that the 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 listRepositoryAttributes operation. See chapter, "Managing Web Services Security" for more information on the header elements.
Use the listRepositoryAttributesRequest elements to set the directory service information.
Use listRepositoryAttributesRequest message and construct the input message by using the details obtained in preceding step.
Invoke the listRepositoryAttributes operation of the ArcorUserRegistryMgmtSvc service to fetch the user attributes.
This operation returns the listRepositoryAttributesResponse 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, listRepositoryAttributesResponse, 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.

The following table provides more information about the elements returned for a successful transaction. See to appendix, "Error Codes" if there are any errors.

Element	Description

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