Skip to content

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

Sign up for GitHub

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

Merged
jiazhai merged 5 commits into from
Jun 27, 2020
Merged

[PIP-55][Doc]--Update security overview #7302

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
af12da9
Update the security overview for PIP 55. the parameter is added to t…
Huanli-Meng Jun 18, 2020
fa7a4a4
Update security overview for PIP-55.
Huanli-Meng Jun 18, 2020
c301106
a redundant space
Huanli-Meng Jun 22, 2020
8c55c9a
doc based on Jennifer's comments
Huanli-Meng Jun 22, 2020
6b90a54
doc based on Jennifer's comments.
Huanli-Meng Jun 22, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions site2/docs/security-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ By default, Pulsar configures no encryption, authentication, or authorization. A

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.

The broker supports learning 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.

@Jennifer88huang-zz Jennifer88huang-zz Jun 19, 2020

Copy link
Copy Markdown
Contributor

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

@Huanli-Meng Huanli-Meng Jun 22, 2020

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated


## Role tokens
Expand Down