For a SAML-based service, a user can click on that service in his home and be redirected to a URL. This URL is set in the service’s “SAML Settings” and usually looks like “https://www.myservice.com/acs”.
What is the corresponding setting for an SCIM service? Right now if the user clicks on the SCIM service, he’ll be redirected to www.okta.com. That’s not surprising, since I as the admin didn’t configure any redirection URL.
Some thoughts:
I’m doing all this in a dev account. Am I not allowed to configure this yet?
Do I need to create a separate SAML service that should also be assigned to the user? I.e. the SCIM service manages user lifecycle on the backend and is not visible to the user. User sees the SAML service in his Okta home page, and can click on that to access the actual service.
Did you ever find a solution here? I’m wondering the same thing:
I can create a SAML 2.0 application in Okta and connect it to my web application, but provisioning is a two step process - add the user to the app in Okta, and create the user with the same email address in the web app
I can create a SCIM application in Okta and connect it to my web application, but the SAML options don’t go far enough - there is no place to configure the ACS URL and other SAML options
Do I need to create two apps? One for SAML auth and one for SCIM provisioning? If so, is there a way to connect the two?
FWIW, OneLogin does this very well: the test app to build off of has both SAML config options and SCIM options.
SCIM templates are created only for provisioning, not single sign-on. The details that are present under Sign On tab are purely for placeholder.
If you have a production tenant and/or you are able to create SAML 2.0 application from the Application Integration Wizard (switch from Developer Console to Classic UI in admin panel >> Applications >> Add Application >> Create New App >> Sign On method >> SAML 2.0), then please send an email to support@okta.com to request SCIM_PROVISIONING feature. This feature will give you the possibility to add provisioning to the SAML applications through SCIM 2.0.