Skip to content
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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

ZavenArra
Copy link
Contributor

No description provided.


## Considered Options

1. Do not implement SSO
Copy link
Contributor

@dadiorchen dadiorchen May 21, 2022

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?

Copy link
Contributor Author

@ZavenArra ZavenArra May 21, 2022

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


### 2. Implement SSO for all providers supported by Keycloak

{example | description | pointer to more information | …} <!-- optional -->

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.

* 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.

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.


### 3. Implement SSO only for providers that are deemed philosophically aligned with values shared by Greenstand engineers.

{example | description | pointer to more information | …} <!-- optional -->

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?

Copy link
Contributor

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 ???

Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants