You need to sign in to do that
Don't have an account?
kiran patil 3
After customer portal licence upgrade we are unable to login using SSO
i am having below issue related to SSO, we use federation id for SSO Login
Background:
We upgraded users from customer portal licence to BMC Remedyforce licence. Those users are unable to log tickets using SSO.
Though they are able to access Remedyforce Application using a site URL and log tickets but using federation id they are unable to login.
Has anyone faced a similar issue, could any one guide me on possible check i should be doing to solve this issue
Below is the SAML Validator response that i am getting
SAML Validator
Help for this Page
Enter your SAML response in base64-encoded, deflated and base64-encoded, or plain xml format into the field below, and click Validate.
The response will be validated against the values configured in the Single Sign-On Settings page.
The validator will try to continue validation even if it finds an error. However, the validator cannot recover from some errors. More errors may be revealed after you fix the initial problem. Additionally, errors not related to the assertion itself will not be detected by this validator. Please refer to the login history for more information on such failures.
Your organization is configured to use SAML Version 2.0
Results
Last recorded SAML login failure: 2014-08-03T08:08:19.376Z
Unexpected Exceptions
Ok
1. Validating the Status
Ok
2. Looking for an Authentication Statement
Ok
3. Looking for a Conditions statement
Ok
4. Checking that the timestamps in the assertion are valid
Ok
5. Checking that the Attribute namespace matches, if provided
Not Provided
6. Miscellaneous format confirmations
Ok
7. Confirming Issuer matches
Ok
8. Confirming a Subject Confirmation was provided and contains valid timestamps
Ok
9. Checking that the Audience matches, if provided
Ok
10. Checking the Recipient
Ok
Organization Id that we expected: 00DD0000000oLWm
Organization Id that we found based on your assertion: 00DD0000000oLWm
11. Validating the Signature
Is the response signed? false
Is the assertion signed? true
Is the correct certificate supplied in the keyinfo? true
Ok
12. Checking that the Site URL Attribute contains a valid site url, if provided
Ok
13. Looking for portal and organization id, if provided
Found portal_id attribute: 060D00000009MPJ
Found organization_id attribute: 00DD0000000oLWm
14. Checking if session security level is valid, if provided
Ok
Background:
We upgraded users from customer portal licence to BMC Remedyforce licence. Those users are unable to log tickets using SSO.
Though they are able to access Remedyforce Application using a site URL and log tickets but using federation id they are unable to login.
Has anyone faced a similar issue, could any one guide me on possible check i should be doing to solve this issue
Below is the SAML Validator response that i am getting
SAML Validator
Help for this Page
Enter your SAML response in base64-encoded, deflated and base64-encoded, or plain xml format into the field below, and click Validate.
The response will be validated against the values configured in the Single Sign-On Settings page.
The validator will try to continue validation even if it finds an error. However, the validator cannot recover from some errors. More errors may be revealed after you fix the initial problem. Additionally, errors not related to the assertion itself will not be detected by this validator. Please refer to the login history for more information on such failures.
Your organization is configured to use SAML Version 2.0
Results
Last recorded SAML login failure: 2014-08-03T08:08:19.376Z
Unexpected Exceptions
Ok
1. Validating the Status
Ok
2. Looking for an Authentication Statement
Ok
3. Looking for a Conditions statement
Ok
4. Checking that the timestamps in the assertion are valid
Ok
5. Checking that the Attribute namespace matches, if provided
Not Provided
6. Miscellaneous format confirmations
Ok
7. Confirming Issuer matches
Ok
8. Confirming a Subject Confirmation was provided and contains valid timestamps
Ok
9. Checking that the Audience matches, if provided
Ok
10. Checking the Recipient
Ok
Organization Id that we expected: 00DD0000000oLWm
Organization Id that we found based on your assertion: 00DD0000000oLWm
11. Validating the Signature
Is the response signed? false
Is the assertion signed? true
Is the correct certificate supplied in the keyinfo? true
Ok
12. Checking that the Site URL Attribute contains a valid site url, if provided
Ok
13. Looking for portal and organization id, if provided
Found portal_id attribute: 060D00000009MPJ
Found organization_id attribute: 00DD0000000oLWm
14. Checking if session security level is valid, if provided
Ok
Can you check if the portal_id attribute matched the portal _id from the Customer Portal settings.
If they do not match, then try to change the ID in the SAML insertion you are sending to SFDC.
Please mark this as a best answer if your query is resolved so others also get help from this thread in future.
Thanks!