You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're normalizing data from OIDC providers to fit the general OpenID Connect Claim model. This is normally working as expected for OIDC certified providers, but non-oidc certified providers like GitHub need some more magic. Any type of enrichment (e.g. "how many repos does the user have?" should be done via an RPC).
We should document what the results of these providers look like. We also need to address that some providers only share a subset of resources, e.g.:
GitHub does not provider family name, first name, etc, nor address and so on
The text was updated successfully, but these errors were encountered:
This patch changes the social sign in guide to represent more use cases such as Google and Facebook. Additionally, the example has been updated to work with Jsonnet.
This patch also documents limitations around merging user data from GitHub.
Closes#49
This patch changes the social sign in guide to represent more use cases such as Google and Facebook. Additionally, the example has been updated to work with Jsonnet.
This patch also documents limitations around merging user data from GitHub.
Closes#49
We're normalizing data from OIDC providers to fit the general OpenID Connect Claim model. This is normally working as expected for OIDC certified providers, but non-oidc certified providers like GitHub need some more magic. Any type of enrichment (e.g. "how many repos does the user have?" should be done via an RPC).
We should document what the results of these providers look like. We also need to address that some providers only share a subset of resources, e.g.:
The text was updated successfully, but these errors were encountered: