McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 206

↗ View in doc context
page
206
source
finesse/v12.5/developer-guide/developer-guide.md
chunk_id
finesse::v12.5::developer-guide::developer-guide::190

Response body returned after the SSO test contains an HTML displaying information about the user and token. This HTML also contains a JavaScript that sends the SSO test status, via window postMessage API, to the parent or opener window. To get the status of SSO test on an older versions of Internet Explorer or any third-party non-browser clients that do not have this API, use the cookie set as part of HTTP response. COOKIES set as part of response: ssotest=true Post message to parent window with below object: { status: "true", errorMessage: "" } Example Response COOKIES set as part of response: ssotest=false Post message to parent window with below object: { status: "false", errorMessage: "AUTH_ERROR"/"NO TOKEN" } Example Failure Response: Single Sign-On—Fetch Access Token This API gets the access token and refresh token from the Finesse server. Invoking this API might involve browser redirect to Cisco Identity Service and Identity Provider. Note https://<FQDN>/desktop/sso/token URI: https://finesse1.xyz.com/desktop/sso/token Example URI: Agents and supervisors can use this API. Security Constraints: GET HTTP Method: — Content Type: JSON Input/Output Format: — HTTP Request: (Optional) return_user=yes|no (Optional) return_refresh_token=true|false Request Parameters: 200: Success 400: Bad Request 401: Unauthorized 500: Internal Server Error HTTP Response: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 190 Cisco Finesse Desktop APIs Single Sign-On—Fetch Access Token

Image 1 from page 206