Repository navigation
fix(auth): org roles, sign-in links and re-auth - #1241
Merged
Merged
Conversation
An organisation's accounts hold one role inside it, Admin or Viewer, through its `<org>-admins` and `<org>-viewers` groups. An organisation admin manages that organisation's accounts and OIDC providers. The last usable admin of an organisation cannot be removed. An organisation's own provider signs in only its accounts and a platform provider signs in only root accounts. A verified IdP email from a provider trusted for its domain links the sign-in to the one account holding that email. A local account must enter its password before the link is made. An admin can unlink a sign-in. Every access change needs a re-auth grant in the X-DFE-Reauth header: accounts (creation included), groups, roles, OIDC providers, API keys, SCIM writes and retiring the bootstrap admin. POST /auth/reauth takes the caller's password and returns a 10-minute grant bound to the caller and one target. An account with no local password signs in again at its own provider through POST /auth/oidc/reauth, which checks the subject and a recent auth_time. A caller signed in with an API key needs no grant. Sessions of an account bound to no organisation carry the organisation that runs the deployment. Accounts report their organisation's display name. The synthetic data stream presents its organisation's ingest token.
Group list and detail responses have a linked_members field: the accounts holding a linked group through an IdP sign-in that asserts it. The members field, which a write stores, stays separate from linked_members, so a group held only through a link no longer looks empty.
|
Released in v1.22.93-rc.1 -- https://github.com/hyperi-io/dfe-engine/releases/tag/v1.22.93-rc.1 |
This file contains hidden or 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.
An organisation's accounts hold one role inside it, Admin or Viewer, through its
<org>-adminsand<org>-viewersgroups. An organisation admin manages that organisation's accounts and OIDC providers. The last usable admin of an organisation cannot be removed. An organisation's own provider signs in only its accounts and a platform provider signs in only root accounts.A verified IdP email from a provider trusted for its domain links the sign-in to the one account holding that email. A local account must enter its password before the link is made. An admin can unlink a sign-in.
Every access change needs a re-auth grant in the X-DFE-Reauth header: accounts (creation included), groups, roles, OIDC providers, API keys, SCIM writes and retiring the bootstrap admin. POST /auth/reauth takes the caller's password and returns a 10-minute grant bound to the caller and one target. An account with no local password signs in again at its own provider through POST /auth/oidc/reauth, which checks the subject and a recent auth_time. A caller signed in with an API key needs no grant.
Sessions of an account bound to no organisation carry the organisation that runs the deployment. Accounts report their organisation's display name. The synthetic data stream presents its organisation's ingest token.