Production-ready with Osso #6
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds SAML SSO support for multiple tenants using Osso and osso-react. omniauth-rails_csrf_protection helps us maintain security with regard to CVE-2015-9284.
SAML Configuration
We use the Osso Demo instance in this branch, available at https://demo.ossoapp.com
The demo instance will have a customer with the domain
example.comconfigured with Osso's Mock IDP.When configuring SAML SSO for a second tenant, you can onboard a customer and configure an Identity Provider via the demo instance, and use the generated documentation to configure the app in an IDP instance. You should sign up for at least one IDP for testing purposes. The demo instance resets data hourly, so this will only be useful for testing purposes.
Sign in UX
We're using Osso's react package, and specifically the
<OssoLogin />component in order to provide a strong user experience for both SAML and email / password based users.