McDewey

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

Page 210

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

{"token": "eyJhbGciOiJkaXIiLCJjdHkiOiJKV1QiLCJlbmMiOiJBM TI4Q0JDLUhTMjU2In0..521UM8q8d7wM5naKgWzPhA.NkhEH 7SatpXPOVqQobJstaZ51HBcMTcIej5qdIJ0ZwjCnV7u8iKGcv7t 5cLYruV6WZFJn8z7iSckXdduDqmRserhBDnbpk-gd5jqNj9r2ZS tfeBZIx6Phng6EMWUjtK9cbrO79MenQ7u7Y3Hhe7P7qvQiaTw keUw7No09NFGat-ICzhHbTF8D4WKFhFefw1J-q55ktcdD-CmM s-KXYrmA8DLltjF9ii9dCYHFfC2nKBETzdYWR2ple4B6_Lv0np g8OSU53LyTT3ObHm6TvWZ09KYrWUWMKNFas73Gx7rYro4 C7Tc4pYb9ZfJmkcT6coRIocMteYCrqCy7ufRqO-BPObNIah_J o2VQ_wwo-5wE-cMUUDpGa5X2nMtP2YUH4sb7b_SHX9Xq_w6 cwLRcBiDXjyGl7Smk1RzF1aXj2A9R06a71VjzmUsjq4UtrT7_IfY s9RrFX9jhnXX1VB8Dqgh-Pnb16rsskRg7TPP4EV9fwDSbhA- oMrMKqFz5BFWMhNaFCHtJQWtXxNRK802ybyzXwR3KGeINS D3dOGj2vWRpnhuTB9veHr9InSrc2s67rspguN7YX2bkIEEQNBC Y3X5rf_UMyGSlPvlArh6b-_yZXk62kXmYJWJ7g1uTRwTaou87C j83fqdaIOYMNIOeZhZqDmKDOZqMmVW_Aj-9-Tn0lTXkKmsPvqt oJYCN1T_3fZrvhzJLImy0whXgEtxc88MYNOCsuPSkIuCRNpoO GgWXATdF1GHPUnQPStW2GsZEfbdY5R1X9x3SZXtngh4XFM gYtMjP129X8pvAT_AY35JtRzpdryRPdAYrEc72tkY_xWLBahpS AKrcX7x8gtMRZmV5HlKs7_sW1amje0gaMKFlqh8i56XWbwnsU SdKLC-LZDtvWZ5wYuHPY1CSwC0oT9lHytWBXo3GSXSv 1iqy75ud6KrvrJg3WG2k_2biqxpc0S9MsATT2WGtGBt5ko2wEcn6 A.l_JfM6gAelSswEeGFAOKwg", "expires_in": 300} Example Response {"errorType": "AUTH_ERROR", "errorData": "refresh-token", "errorMessage": "Invalid Token"} Example Failure Response: If the token was initially fetched with the return_refresh_token=true query parameter, the refresh token query parameter with the value of the current refresh token is mandatory. Note Troubleshooting Steps 1. Validate that the requests are reaching Finesse by checking the Finesse tomcat_access_logs. 2. For any errors on the token refresh, check the Finesse Valve logs. 3. If the request reached Finesse access logs and there are no errors in Finesse Valve logs, check the IdS error logs for more details. It contains the reason for the error. Single Sign-On—Get User Authentication Mode This API allows a client to get the authentication mode of a user in a Unified CCE deployment that is in hybrid mode (SSO and non-SSO). This API uses either the username or userId and it does not require authentication. This API does not require HTTP authentication. The third-party integrations must configure this API to determine which authentication mode (SSO or non-SSO) is configured for the user. If required, this API can be disabled using CLI. By default, the CLI sets the value of this property as true. utils finesse set_property webservices enableUserAuthMode {true|false} For more information, see Service Properties section in Cisco Finesse Administration Guide at https://www.cisco.com/c/en/us/support/customer-collaboration/finesse/products-maintenance-guides-list.html. Note Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 194 Cisco Finesse Desktop APIs Single Sign-On—Get User Authentication Mode