Hello,

I am looking to integrate an app for SSO using SAML. I can currently successfully log a hardcoded tenant through using SSO locations such as:

http://localhost/okta/simplesamlphp/www/module.php/saml/sp/saml2-acs.php/exampleone

http://localhost/okta/simplesamlphp/www/module.php/saml/sp/saml2-acs.php/exampletwo

http://localhost/okta/simplesamlphp/www/module.php/saml/sp/saml2-acs.php/examplethree

Where the value after the saml2-acs.php is the authentication source to identify the user's organisation, however when configuring other apps already set up from other vendors this input doesn't appear to be available to be changed, so this method doesn't appear to be available to use in production.

Other vendors appear to have a subdomain option in their app set ups, however I can't find a way to enable this in our development one using the SAML app wizard, nor find any resources that cover multi-tenancy when setting up an Okta app.

Currently the method I have found, which appears to be configurable in a production environment, is using the relaystate to pass the organisation identifier.

Are you able provide any advice on how to configure an app to allow for some sort of identification of the organisation that would work in production or to suggest any resources that might help with this?

Any help in this matter is greatly appreciated.