/mcp" + exp.toString()); } } SSO Cookie JTAPI supports authentication using SSO Cookie from Release 10.0.1 and later. An SSO Cookie, once generated, is valid for the entire session. The cookie can be reused during that session. SSO Cookie is supported only on a Secure Connection. Cisco JTAPI does not allow authentication using SSO Cookie over non-secure connections. Applications must also provide the fully qualified name of the client and server certificates in the providerString. The following new keywords are being introduced to be used in the provider string : ssocookie, cCert, sCert. The providerString must be in the following format when using an SSO Cookie: providerString = "ssocookie = <cookie>;cCert = <fully qualified client certificate>;sCert = <fully qualified server certificate>;" Interface Changes See CiscoJtapiException, on page 416 Message Sequences See Single Sign-On, on page 1474 Backward Compatibility This feature is backward compatible. Single Step Transfer This interface allows applications to transfer a call to an address. Cisco Unified JTAPI continues to support this interface as defined in JTAPI 1.2 specification, but the events that are delivered to applications are changed from the previous versions of Cisco Unified JTAPI. In previous versions of Cisco Unified JTAPI, the original call goes to a held state, and a new call gets created between the transfer controller and destination when applications use this interface. After successful completion of transfer, both calls on transfer controller go to an IDLE state. If a transfer fails, the original call remains in Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 171 Features Supported by Cisco Unified JTAPI Single Step Transfer