Skip to content

Conversation

@Huanli-Meng
Copy link
Contributor

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

@Huanli-Meng
Copy link
Contributor Author

@jiazhai , please help review the document.

@Huanli-Meng
Copy link
Contributor Author

once the doc is approved, it will be added to the release 2.6.0.

@Jennifer88huang-zz Jennifer88huang-zz added doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. area/security labels Jun 19, 2020
@Jennifer88huang-zz Jennifer88huang-zz added this to the 2.7.0 milestone Jun 19, 2020
Copy link
Contributor

@Jennifer88huang-zz Jennifer88huang-zz left a 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.


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 .
Copy link
Contributor

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.
Copy link
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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated

@jiazhai jiazhai merged commit 29b81ed into apache:master Jun 27, 2020
wolfstudy pushed a commit that referenced this pull request Jul 29, 2020
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)
huangdx0726 pushed a commit to huangdx0726/pulsar that referenced this pull request Aug 24, 2020
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/security doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. release/2.6.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants