/mcpTo get a list of both voice and nonvoice dialogs for a user, use the User - Get List of Dialogs (Voice Only by Default) API. User - Sign Out and User - Change State with Reason Code APIs You can sign a user out of all Media Routing Domains when the user signs out of the desktop, using either the User - Sign Out API or the User - Change State with Reason Code API. The desktop sign out fails only if the voice MRD sign out fails; it is not impacted by nonvoice MRD sign out failure. Single Sign-On Single Sign-On (SSO) is a mechanism to authenticate users across software systems using a common LDAP identity and this common authentication service provides a token. Multiple applications use this token to authenticate the user across preconfigured applications. The Single Sign-On (SSO) APIs are used in the Finesse desktop for token related operations and are ready to use in an out of the box Finesse deployment. Third-party desktop applications have to use these APIs independently for SSO token related operations. Single Sign-On Components The following are the SSO components: Identity Provider (IdP) • IdP is an application that creates, maintains, and manages identity information for users. • IdP offers the user authentication as a service. Third-party applications (for example, web applications) outsource the user authentication mechanism to a trusted IdP which is configured within the Organization. For example, Active Directory Windows Server. Cisco Identity Service (IdS) • Cisco IdS is the common API endpoint for relaying requests to the IdP by generating the authentication token and validating it. • Cisco IdS implements an authorization endpoint and token endpoint as part of its OAuth (Open Authorization) server implementation. Token Types The following are the token types: • Access Token—It accesses protected resources. Clients are issued an access token that contains identity information for the user that is encrypted by default. For an SSO enabled user, use the access token in the authorization header of the Finesse REST APIs. Authorization: Bearer <access token> Note Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 188 Cisco Finesse Desktop APIs Single Sign-On