We are planning to migrate from partner portal to community. In the current functionality users are able to login from an internal portal to salesforce as the SSO is configured. I read thru the communities documentation and they say that the login url for the community needs to be changed communityUrl + '/login'.

1) Does this mean that this communityUrl + '/login' will be part of the relayState of the SAML?

2) if not , then will we have to change the Salesforce endpoint in the SAML assertion to this communityUrl+'/login'? If we do this then the current functionality gets impacted, right?

3) Or Do we need to set up multiple SSO configs in Salesforce and then provided one for internal user and the other for community?

Please advise.


1 Answer 1

  1. No
  2. Yes, you have to change the URL if you're migrating to the community. If this is what you mean by 'impacted', then yes. You should be using an identity provider that does not expose this URL to end users.
  3. Maybe, see below

Internal users can login to the community via the same Assertion Consumer Service (ACS) endpoint @ /login/blah used by community users. You don't need multiple connections on the identity provider side.

With communities it is now much easier to segregate audiences vis-a-vis the baseline org. For example, we have customers where internal users (full Salesforce license) login to the baseline org and external users login to the community. They use two different ACS endpoints on two different identity providers. Or you could have a single identity provider with two connections, one for each user segment. This depends on the sophistication of your identity provider.

  • In our case we just have one identity provider and earlier the we used have portalId in the URL to route the user to the partner portal. So from your answer I pick up that we might need to have 2 connections to the IDP, one for internal (the existing one) and another for community (endpoint will be communityUrl+/login). Another point to note that our internal users will never access community and vice-versa.
    – Sam
    Nov 16, 2013 at 3:06
  • If internal users will never access the community and vice versa, then you'll need two endpoints, one for the community with /login and one for base org. Some IdPs can actually handle this scenario with 1 connection but typically it'll require 2.
    – identigral
    Nov 18, 2013 at 8:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.