In our Salesforce Org, our internal users sign on via Single Sign On in our Identity Provider, Okta. We are looking use Okta for our partner community users as well, and to do so, we need to add a separate connector to Salesforce.
It appears that I will need to enable multiple SAML configurations to do so. This is an irrevocable action, and I want to, first, make sure that this is necessary, and second, make sure that this does not break anything before moving forward. I receive the following message:
- Once you enable this feature, you can't disable it.
- You will not be able to use SAML 1.1 once this feature is enabled.
- Audience will berequired in all SAML Responses.
- Your existing single sign-on configuration will be converted, and you will be able to create multiple SAML 2.0 configurations for your organization.
- A new Self-Signed Certificate will be created and used to sign SAML Requests.
- Your Salesforce Login URL will change from https://login.salesforce.com to https://mycompany.my.salesforce.com?so=00D40000000XXXX. This may cause users to be unable to log in using SAML.
- SAML Responses that can't be parsed will no longer result in login history for your organization. Please ensure your Identity Provider generates valid SAML Responses using the SAML Validator.
Will this be a necessity to enable SSO for the partner community? We do need to have separate connectors because we are using a partner login feature in Okta. If so, then when it says the Salesforce Login URL will change, will that affect logins from other sources (From web browser, connected apps, etc.)? I want to make sure that once the connector is updated with the new certificate and URL, no configuration or integrations outside of our IDP will need to be changed.