
ArunB.42669 (Customer) asked a question.
I am trying to create a community integration with Salesforce using JIT. The idea is to enable SSO for all the students. I followed all the steps given in the SAML 2.0 set up instructions in OKTA but still getting "Unable to map the subject to a Salesforce.com user" error on the Salesforce side. I read the blogs on the Salesforce side as well but it seems that I am missing something while adding adding the application on the OKTA side. FYI, I used salesforce.com application with out federation ID.

Hi Arun,
In this scenario you will need to ensure that you have API Provisioning turned on so that new users / accounts can be created in Salesforce upon being directed there from Okta. If you have further issues with this setup I would recommend opening a support case to go over more in depth your setup.
Thank you,
Brooks Johnson
Okta Support Engineer
Hi Arun,
Check your Salesforce app settings if you have below values..
SAML Type: Assertion contains the Federation ID from the User object
SAML identity location: Identity is in the NameIdentifier element of the Subject statement
If its still not working, try creating OKTA app by clicking --> Create new app--> Web --> SAML2.0. Post creating app in OKTA, import okta metadata into Salesforce app with above values matching...
Thanks
Siva Desetti
Thx Siva and Brooks!
Hi Arun, if one of these responses solved your questions, can you mark it as Best Answer? Thanks =)
Hi Siva and Brooks,
I followed the steps you mentioned in your answer but still getting the same error.
Thanks,
Arun
I am having this problem as well. Okta is NOT sending the FederatedID to Salesforce in the location that Salesforce is expecting it. The FederationID is not present ANYWHERE in the SAML.
I am also having the same problem. In fact, I am not even able to enable provisioning because when I test the API credentials it cannot connect to the administrator account (the username, pw, and token are all correct for the corresponding admin account).
I'm currently working with a vendor, experiencing the very same issue. I do not have access to their SalesForce admin portal but i'm working on the Okta side. Okta Support has confirmed all is well on my end but for some reasons, they are getting the "Unable to map the subject to a Salesforce.com user".
Any help will be appreciated.
Thanks