function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Robin BarnwellRobin Barnwell 

Single Sign-on Set-up - aaaarrrggghhhh!!!!!

I just can't work this out.  I've read and re-read the Salesforce documentation.  All I want to do is connect my Community to the internal Identity Provider.

1. I have a Salesforce Org with a Community, nothing special - community is active and published, standard template, no customization

2. I set-up My Domain and this automatically creates a SAML idetnity provider for the new domain.  It included a self-signed certificate plus metadata end-points for the Domain and the Community Domain.

3. I set-up both domains as Remote Sites so I can then set them up for SSO

4. I enable Single Sign-on and set-up the Community as per the instructions:
To set up a community as a service provider, use the community URL under SAML Metadata Discovery Endpoints on the Identity Provider page. Upload the SAML metadata from this URL. Using the metadata populates the service provider’s SAML SSO settings, including the Login URL that points to the community. When you define a connected app on the identity provider, specify this Login URL as the ACS URL.

5. I set-up the community as a connected app and use the Entity ID and HTTPRedirect URL specified

6. I update the community to enable access to this SSO login.  I get it showing on the login screen, but it doesn't work.  What can I do to debug this??

Community Login Page

SSO Page - no login
Robin BarnwellRobin Barnwell
I've got a SAML assertion validator trace if that helps
Unexpected Exceptions
1. Validating the Status
2. Looking for an Authentication Statement
3. Looking for a Conditions statement
4. Checking that the timestamps in the assertion are valid
5. Checking that the Attribute namespace matches, if provided
  Not Provided
6. Miscellaneous format confirmations
7. Confirming Issuer matches
8. Confirming a Subject Confirmation was provided and contains valid timestamps
9. Checking that the Audience matches
10. Checking the Recipient
  Incorrect recipient
  Recipient that we found in the assertion:
  Recipients that we expected based on the Single Sign-On Settings page:
  Regular flow:
  OAuth2 flow:
  MyDomain Regular flow:
  MyDomain OAuth2 flow:
  Warning: Salesforce custom domains (such as those created using My Domain) must be all lowercase.
  Organization Id that we expected: 00D6E0000008z9w
  Organization Id that we found based on your assertion: null
11. Validating the Signature
  Is the response signed? true
  Is the assertion signed? true
  The reference in the response signature is valid
  The signature in the assertion is not valid
  The reference in the assertion signature is valid
  Is the correct certificate supplied in the keyinfo? true
  Signature or certificate problems
  The signature in the response is not valid
12. Checking that the Site URL Attribute contains a valid site url, if provided
  Not Provided
13. Looking for portal and organization id, if provided
  Not Provided
14. Checking if session security level is valid, if provided

Vijay GurusamyVijay Gurusamy
How did you resove this isue and set up sso for communities ?
Robin BarnwellRobin Barnwell
I had a long call with the Product Manager at Salesforce.  It turns out there is no such thing as SSO between a Salesforce Community and the Org that it is part of.  So there is no set-up required.
Do you know what the ?so=00D6E0000008z9w parameter is for in your information above? I am having some SSO problems also, and my OKTA documentation says to use the ?so= parameter, but I cant find anywhere where it tells me what the "so" is referencing. All help appreciated!
Robin BarnwellRobin Barnwell
I think will be the Salesforce Org Id