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

   Rename the built-in IDP page to "Local users and groups". The feature is a 
local user store backing HTTP Basic authentication. BasicAuthenticator checks a 
password against stored hashes and returns a principal. Nothing is issued and 
no other service can rely on it, so "identity provider" claimed something the 
feature does not do, which is why the old page had to spend a paragraph 
disclaiming it. The idp-basic plugin id and the /api/idp paths are unchanged, 
and the page explains why.
   
   Remove security.md. It duplicated the sidebar as a list of empty headings, 
had already gone stale, and the category can generate its own index.
   
   Correct authorization-pushdown.md, which described pushdown to MySQL and 
BigQuery that does not exist. v1.3.0 ships two providers, ranger and chain, and 
chain composes Ranger plugins rather than reaching another system. Adds the 
missing authorization.ranger.hadoop.security.authorization property and fixes 
the HiveDriver default, which had lost its final character.
   
   Collapse the duplicate per-prefix tables in the CORS and HTTPS pages, and 
note that the shipped CORS defaults of allowedOrigins=* with 
allowCredentials=true are a combination browsers reject.
   
   Renaming the page meant renaming the concept, so the connector, gvfs and 
OpenAPI docs move to the new wording as well, and links from the two removed 
pages are retargeted.
   
   Follow-ups not in this PR:
   
   - `ALLOWED_METHODS` in `JettyServerConfig` has a doc string that disagrees 
with its own default.
   - gravitino-site needs the Security category link changed to a generated 
index and a redirect for the renamed slug.
   - `how-to-authenticate.md` states the `simple` incompatibility twice, at 
lines 58 and 386.


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