Authentication

Client Contract 1

Overview

Client Contract 1 (CC1) uses basic authentication for all requests and oprates under https: (SSL). No access is permitted under http:

It uses SOAP based RPC methodology with WSDL definitions for methods, enumerations, and complex data types.

Credentials

Execution of any method within the service will require a valid Attendance on Demand client access account. The access account used will determine the level of access permitted on the client database.

Access accounts are supplied by Attendance on Demand, an Attendance on Demand Channel Partner, or by an individual client. It is recommended that the access account used for web service is not also shared by a user. Modifications to a client database using an access account through web services are logged in the same way as user changes.

SOAP Endpoint

When building your client access code, it is important to correctly specify the SOAP endpoint (which is invoked over HTTP) properly for each client. CC1 is a client based contract and the client is identified within the sub-domain portion (URI) of the URL.

Example: https://[yourURI].attendanceondemand.com:8192/cc1exec.aew/soap/IAeXMLBridge

Authentication is required at this level. You must supply a valid access account and password using basic authentication in order to invoke any CC1 specified methods.

This URL is returned within the WSDL specification (usually at the end) under the elements “service”, “port” and “soap:address”. The “soap:address” is the endpoint. If you re-contract on a per client basis, the endpoint will automatically adjust to contain the client URI.

The contract is static across all clients. It is safe to change the client portion of the endpoint (client URI) at any time for any clients your account has access to.

A reserved port number is used to acess the WSDL specification and to invoke remote methods. This port number is 8192 and must be present on all requests.