|Note:||The Access Web Service is not deployed in a standard installation.|
|Note:||It is deprecated and should only be used by older, existing applications, in order to provide a migration path for these applications. WebLogic Server Web Services security cannot be used when using the Access Web Service and must be turned off in Oracle Communications Services Gatekeeper to be able to use the Access Web Service.|
The Access Web Service contains operations for establishing a session with Oracle Communications Services Gatekeeper, changing the application’s password, querying the amount of time remaining in the session, refreshing the session, and terminating the session.
Before an application can perform any operations on the Parlay X or Extended Web Services interfaces, a session must be established with Oracle Communications Services Gatekeeper. When a session is established, a session ID (loginTicket) is returned which must be used in each subsequent operation towards Oracle Communications Services Gatekeeper.
The loginTicket shall be present in the SOAP Header element Security, see below. Once the login ticket is acquired, it must be sent in the SOAP header together with a username/password combination each time a Web Service method is invoked. See Examples.
The WSDL for the Access Web Service can be found at
where host and port depend on the Oracle Communications Services Gatekeeper deployment.
Operations to establish a session, change a password, get the remaining lifetime of a session, refresh a session and destroy a session.
Logs the application into the Oracle Communications Services Gatekeeper and retrieves a login ticket. This login ticket represents the session and must be added to the SOAP header of every subsequent request that the application makes to the Oracle Communications Services Gatekeeper.
In most cases, the login ticket is only valid for a certain time interval, set by the operator. Once the time period has expired, the application has a second operator-set time period to refresh the login ticket. Until the ticket is refreshed, the application can not make any other requests. The operation used to refresh the ticket is refreshLoginTicket, see Operation: refreshLoginTicket. If the ticket is not refreshed during this second period, the session is destroyed, and the application must log back in.
ID of the login-session. This ID is used for each request towards Oracle Communications Services Gatekeeper. It must be included in the SOAP header of every subsequent request.
Logs an application out of the Oracle Communications Services Gatekeeper. Destroys the login session and the corresponding login ticket.
Changes the password for an application.
Reports the remaining amount of time the login ticket is valid.
Refreshes the login ticket. This refreshed login ticket must be provided in the SOAP header in all subsequent method calls. The login ticket can be refreshed for a limited, operator-set time interval after the previous login ticket has expired. If this time interval expires, the application must login again. Oracle Communications Services Gatekeeper expiration timers are reset, but the same login ticket is returned.
Exceptions of this type are raised when there are error conditions related to the Access Web Service. Other error conditions are reported using the exception GeneralException.
Exceptions of this type are raised when the applications session has expired or there are communication problems with the underlying platform.
The loginTicket shall be present in the SOAP Header element Security, see below. Once the login ticket is acquired, it must be sent in the SOAP header together with a username/password combination each time a Web Service method is invoked.
The Access Web Service uses a security header described below.
The loginTicket is supplied in the Password attribute.
Below is an example of how to add an Access security header using Axis. The Username attribute must be present but is not used. The header must be added to the Web Service request.
org.apache.axis.message.SOAPHeaderElement header =
new org.apache.axis.message.SOAPHeaderElement(wsdlUrl, "Security", "");
header.addAttribute(wsdlUrl, "Username", ""+userName);
header.addAttribute(wsdlUrl, "Password", ""+loginTicket);