-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[PIP-55][Doc]--Update security overview #7302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…e broker config file by Jia.
|
@jiazhai , please help review the document. |
|
once the doc is approved, it will be added to the release 2.6.0. |
Jennifer88huang-zz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job from technical writing perspective.
site2/docs/security-overview.md
Outdated
|
|
||
| Pulsar supports a pluggable authentication mechanism. And Pulsar clients use this mechanism to authenticate with brokers and proxies. You can also configure Pulsar to support multiple authentication sources. | ||
|
|
||
| The Pulsar broker validates the authentication credentials when a connection is established. After the initial connection is authenticated, the "principal" token is stored for authorization though the connection is not re-authenticated. The broker periodically checks the expiration status of every `ServerCnx` object. You can set the `authenticationRefreshCheckSeconds` on the broker to control the frequency to check the expiration status. By default, the `authenticationRefreshCheckSeconds` is set to 60s. When the authentication is expired, the broker forces to re-authenticate the connection. If the re-authentication fails, the broker disconnects the client . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove the redundant space before the last period.
|
|
||
| The broker knows whether a particular client supports authentication refreshing. If a client supports authentication refreshing and the credential is expired, the authentication provider calls the `refreshAuthentication` method to initiate the refreshing process. If a client does not support authentication refreshing and the credential is expired, the broker disconnects the client. | ||
|
|
||
| You had better secure the service components in your Apache Pulsar deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"knows" is not a good verb here, we can use another verb to avoid attributing human qualities to software or hardware.
For details, refer to attribute human qualities to software or hardware
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
This PR is to update docs for PIP-55: #6074 ### Motivation provide general doc description about implementing the authentication refreshing functionality. ### Modifications Update the Security overview for PIP 55. the `authenticationRefreshCheckSeconds` config has been added through the PR: #6074 (cherry picked from commit 29b81ed)
This PR is to update docs for PIP-55: apache#6074 ### Motivation provide general doc description about implementing the authentication refreshing functionality. ### Modifications Update the Security overview for PIP 55. the `authenticationRefreshCheckSeconds` config has been added through the PR: apache#6074
This PR is to update docs for PIP-55: #6074
Motivation
provide general doc description about implementing the authentication refreshing functionality.
Modifications
Update the Security overview for PIP 55.
the
authenticationRefreshCheckSecondsconfig has been added through the PR: #6074