Jump to: navigation, search
(Update with the copy of version: 8.5.2DRAFT)
Line 1: Line 1:
−
=Authentication Flow=
+
=Web Services Authentication Flow=
 
__NOTOC__
 
__NOTOC__
−
Genesys Web Services authentication is performed in the following sequence:
+
Workspace Web Edition & Web Services provides authentication in the following sequence:
  
−
====Case 1 - Salesforce Authentication====
+
====1. Salesforce Authentication====
 
* Enters here if a request contains two specific headers (Salesforce Session ID and Salesforce Identity URL).
 
* Enters here if a request contains two specific headers (Salesforce Session ID and Salesforce Identity URL).
−
* If successful, the user get authenticated and execution flow proceeds to the authorization stage.
+
* If successful, the user is authenticated and execution flow proceeds to the authorization stage.
 
* If authentication headers are not present or authentication fails, execution flow proceeds to the next step.
 
* If authentication headers are not present or authentication fails, execution flow proceeds to the next step.
  
−
====Case 2 - Configuration Server (CME) Authentication====
+
====2. Oracle Service Cloud Authentication====
 +
* Only enters here if a request contains specific headers (<tt>RNURL, RNSID, RNUSERNAME</tt>).
 +
* If successful, the user get authenticated and execution flow proceeds to the authorization stage.
 +
* If authentication headers are not present or authentication fails, execution flow proceeds to the next step.
 +
 
 +
====3. Configuration Server (CME) Authentication====
 
* Enters here if a request contains basic authentication header and CME authentication is enabled for this contact center.
 
* Enters here if a request contains basic authentication header and CME authentication is enabled for this contact center.
 
* If successful, user is authenticated and execution flow proceeds to the authorization stage.
 
* If successful, user is authenticated and execution flow proceeds to the authorization stage.
 
* If authentication headers are not present, CME authentication is disabled, or authentication fails, execution flow proceeds to the next step.
 
* If authentication headers are not present, CME authentication is disabled, or authentication fails, execution flow proceeds to the next step.
  
−
====Case 3 - Genesys Web Services/HTCC Authentication====
+
====4. Genesys Web Services Authentication====
 
* Enters here if a request contains basic authentication header.
 
* Enters here if a request contains basic authentication header.
 
* If successful, user is authenticated and execution flow proceeds to the authorization stage.
 
* If successful, user is authenticated and execution flow proceeds to the authorization stage.
 
* If authentication headers are not present or authentication fails, execution flow proceeds to the next step.
 
* If authentication headers are not present or authentication fails, execution flow proceeds to the next step.
  
−
====Case 4 - Security Assertion Markup Language (SAML) Authentication====
+
====5. Security Assertion Markup Language (SAML) Authentication====
 
* Enters here if SAML is enabled and configured.
 
* Enters here if SAML is enabled and configured.
−
* An attempt is made to authenticate user going through various scenarios (Case 1 or Case 2).
+
* An attempt is made to authenticate user through the standard SAML authentication flows.
−
* If case of failure, user receives an anonymous authentication. User will only be given access to unprotected endpoints.
+
* If successful, the user is authenticated and execution flow proceeds to the authorization stage.
 +
* If not successful, the user receives an anonymous authentication, which means this users is only given access to unprotected endpoints.  
 +
 
 +
==Next Step==
 +
*[[Security|Back to Configuring Security]]
  
 
[[Category:V:HTCC:8.5.2]]
 
[[Category:V:HTCC:8.5.2]]

Revision as of 18:37, April 3, 2015

Web Services Authentication Flow

Workspace Web Edition & Web Services provides authentication in the following sequence:

1. Salesforce Authentication

  • Enters here if a request contains two specific headers (Salesforce Session ID and Salesforce Identity URL).
  • If successful, the user is authenticated and execution flow proceeds to the authorization stage.
  • If authentication headers are not present or authentication fails, execution flow proceeds to the next step.

2. Oracle Service Cloud Authentication

  • Only enters here if a request contains specific headers (RNURL, RNSID, RNUSERNAME).
  • If successful, the user get authenticated and execution flow proceeds to the authorization stage.
  • If authentication headers are not present or authentication fails, execution flow proceeds to the next step.

3. Configuration Server (CME) Authentication

  • Enters here if a request contains basic authentication header and CME authentication is enabled for this contact center.
  • If successful, user is authenticated and execution flow proceeds to the authorization stage.
  • If authentication headers are not present, CME authentication is disabled, or authentication fails, execution flow proceeds to the next step.

4. Genesys Web Services Authentication

  • Enters here if a request contains basic authentication header.
  • If successful, user is authenticated and execution flow proceeds to the authorization stage.
  • If authentication headers are not present or authentication fails, execution flow proceeds to the next step.

5. Security Assertion Markup Language (SAML) Authentication

  • Enters here if SAML is enabled and configured.
  • An attempt is made to authenticate user through the standard SAML authentication flows.
  • If successful, the user is authenticated and execution flow proceeds to the authorization stage.
  • If not successful, the user receives an anonymous authentication, which means this users is only given access to unprotected endpoints.

Next Step

Comments or questions about this documentation? Contact us for support!