KB0014353: SSO request/response. How to catch SAML request/response troubleshooting guide.


Issue Description:
 
Unable to login to OSS via SSO
 
Troubleshoot SSO login issues:
 
1. Clean browser's caches or open new browser
2. Click on the SSO link  
3. You might either be redirected to your IdP login page or will be end up at e-SignLive login page with an error message. Do not try to enter username/password on e-SignLive login page.
4. If you are end at e-SignLive login page with an error message, please try to catch the SAMLRequest and SAMLResponse and send to us for investigation.
 
 
How to catch SAMLRequest and SAMLResponse:
 
a. From your browser, open developer tool. In network Tab, Enable "Preserve log" to keep all web traffic.
b. When you enter the link above, you will be redirect to your IdP server with SAMLRequest on the redirect URL.
c. If you are not authenticated with your idp server, please enter your username and password with your IdP server.
d. Your IdP server will make a POST with SAMLResponse.
e. To view the SAML response, search for name "e-signlive" and click on it
f.  In Payload tab, you can see the SAMLResponse
g. Notice Encrypted SAML response. Please provide us the Encrypted response. 
 
 
 
 
 
 
 
SAMLResponse, which sent back from IdP server, must include the following information:
        
1.      e-SignLive expects s valid SAML Assertion with SUCCESS status
2.      e-SignLive expects "email", "first name" and "last name” to be included in SAML Response sent back from IdP server. The expected information should come with the following possible attributes (case insensitive):
a)      For email, possible attributes are: "email", "emailaddress", "mail"
b)      For first name, possible attributes are: "firstname", "givenname","cn"
c)      For last name, possible attributes are: "lastname", "surname", "sn"
3.      e-SignLive also expects <NameID> as part of <Subject> in SAML Response.