-
Notifications
You must be signed in to change notification settings - Fork 12
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
First draft of 0003-use-of-single-signon #3
base: main
Are you sure you want to change the base?
Conversation
0003-use-of-single-signon.md
Outdated
|
||
## Considered Options | ||
|
||
1. Do not implement SSO |
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.
@ZavenArra Can you explain a little more about this, you mean, don't use Keycloak at all or use Keycloak but do not support 3rd part provider, which means use the built-in user account provider in Keycloak?
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.
The meaning is that we would not support 3rd party provider in this option
0003-use-of-single-signon.md
Outdated
|
||
### 2. Implement SSO for all providers supported by Keycloak | ||
|
||
{example | description | pointer to more information | …} <!-- optional --> |
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.
From https://www.keycloak.org/docs/latest/server_admin/
With Keycloak, users can log in to your application using a social network account. Supported providers include Twitter, Facebook, Google, LinkedIn, Instagram, Microsoft, PayPal, Openshift v3, GitHub, GitLab, Bitbucket, and Stack Overflow.
0003-use-of-single-signon.md
Outdated
* Bad, because {argument c} | ||
* … <!-- numbers of pros and cons can vary --> | ||
|
||
### 3. Implement SSO only for providers that are deemed philosophically aligned with values shared by Greenstand engineers. |
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 this is the right way to go. Lots of users make heavy use of social login options to minimise password fatigue.
We just need to determine the right list, which will be an intersection of the most popular providers amongst our user group and the providers with the right values.
0003-use-of-single-signon.md
Outdated
|
||
### 3. Implement SSO only for providers that are deemed philosophically aligned with values shared by Greenstand engineers. | ||
|
||
{example | description | pointer to more information | …} <!-- optional --> |
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.
Can we list the providers we'd like to include?
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.
are you talking about a list like google, facebook, instagram, twitter, linkedin ???
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.
@sebastiangaertner yes, we would like a list of social login providers that are appealing to the Greenstand Engineers.
No description provided.