lasdf1234 opened a new pull request, #10883:
URL: https://github.com/apache/gravitino/pull/10883

   ### What changes were proposed in this pull request?
   
   This PR adds a new design document, `design-docs/gravitino-local-idp.md`, 
for Local IDP support in Gravitino.
   
   The document covers:
   - the motivation and goals for introducing a built-in local IDP mode
   - the Basic authentication model and related configuration
   - password hashing design based on Argon2id
   - the local identity data model, including `local_user_meta`, 
`local_group_meta`, and `local_group_user_rel`
   - the logical mapping between local identity tables and existing `user_meta` 
/ `group_meta`
   - bootstrap account behavior
   - authentication flow and transport security considerations
   - local user/group/password management APIs
   
   ### Why are the changes needed?
   
   Gravitino currently relies on external identity providers for OAuth-based 
authentication. That works well in enterprise environments, but it creates 
friction for POC, offline, isolated, and emergency-fallback scenarios.
   
   This design document captures a lightweight Local IDP proposal so the 
feature scope, storage model, authentication flow, and management APIs are 
clearly defined before implementation.
   
   Fix: N/A
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes.
   
   It adds a new design document describing the proposed Local IDP feature, 
including:
   - a new `basic` authenticator mode
   - a proposed `gravitino.authenticator.basic.algorithm` configuration key
   - new local identity management APIs for users, groups, group membership, 
and password changes
   
   ### How was this patch tested?
   
   Documentation-only change.
   Reviewed the document structure and aligned it with the existing 
`design-docs` style.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to