[improve][doc] Improve the authentication enablement workflow across multiple providers #18035
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.
Motivation
Improve the doc set of the Security chapter to provide Pulsar users with an easy-to-use and easy-to-understand information experience.
This PR attempts to align the workflow to enable Athenz/JWT/OAuth2/Keberos authentication with TLS/Basic Auth. Currently, the described workflow lacks clear logic and seems to be very different with each other. Outdated information will be refreshed as well.
Previously related work: #17615, #17666 and #17808.
Modifications
How it works in Pulsarfor authentication.Many thanks to @nodece for providing technical inputs.
Preview
Overview

Documentation
docdoc-requireddoc-not-neededdoc-complete