-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add single sign on documentation #792
Add single sign on documentation #792
Conversation
ba8ab91
to
cc0707f
Compare
Is it possible to redirect every user to the IAM-system - no matter which e-mail they are entering for login? |
@Kurt108 not yet but think we could add support for something like a |
alright. I will upgrade our current installation and hope our developer can provide the contribution. |
bundles/security/index.rst
Outdated
+ providers: | ||
+ 'sulu.io': | ||
+ dsn: 'openid://%env(resolve:SULU_OPEN_ID_CLIENT_ID)%:%env(resolve:SULU_OPEN_ID_CLIENT_SECRET)%@%env(resolve:SULU_OPEN_ID_ENDPOINT)%' | ||
+ user_role: 'USER' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While write the blog post I'm asking if we should name this role
or role_key
. The user role entity is a different one 🤔 /cc @chirimoya @Prokyonn
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
default_role
, default_role_key
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think default_role_key
is the most accurate, I'd go with that
Co-authored-by: Prokyonn <[email protected]>
What's in this PR?
Documentation for Single Sign on configuration.
Why?
To document the new feature