The OTP server manages information about user identifiers and OTP lists. The URI format used with these entities is as follows:
The application context. This part of the address is typically
. UAS_URL is defined in win32.config or unix.config.
Name of SSO server authentication method, example "otp.1"
Specifies entity type, one of "otp-list" or "user-info"
Unique entity identifierWell known identifiers such as _batch, _query, _all etc. may be used
Request parameters are given in URL parameters. For HTTP POST messages the message body may also be used using "application/x-www-form-urlencoded " encoding.
In the future other request parameter encodings such as XML or JSON may be supported.
If the message body is used for request parameters then the http request header Content-Type must specify the encoding type.
The response message is encoded in XML format using the OTP server XML schema. The http response content type is "application/xml".
Error conditions are indicated by HTTP status codes.
- 200 OK
The operation was successful. Response body contains the requested resource.
- 204 No Content
The operation was successful. Response body is empty.
- 401 Unauthorized
Required by http basic authentication.
- 403 Forbidden
The operation is not allowed.
- 404 Not Found
The resource was not found.
- 405 Method Not Allowed
The http method is not valid
- 500 Server Error
Any other unspecified error
If the error response is produced by OTP Server then a <error> element is returned.