Skip to content

Conversation

@rdhabalia
Copy link
Contributor

Motivation

Right now, broker authenticates client only at the time of opening the connection and this connection become valid for it's lifetime and client can produce/consume messages on this connection even though auth-data provided on that connection is expired. So, we want to close/renew such connections which are expired on the broker.
So, right now, broker doesn't close the expired connection and broker-client don't have capability to renew the connection without closing it.

Modification

Add option in broker to renew connection by asking client to resend renewed auth-data without closing the connection. If client fails to send refreshed-valid auth-data then broker closes the connection.

Result

Broker will have capability to check connection expiry after the auth-data is expired and broker can close the expired connection. This feature will be disabled by default.

@rdhabalia rdhabalia added this to the 2.3.1 milestone Feb 27, 2019
@rdhabalia rdhabalia self-assigned this Feb 27, 2019
@merlimat
Copy link
Contributor

@rdhabalia Since this is not a fix or a trivial change, I'd move this to 2.4.0 rather than 2.3.1

@merlimat merlimat added the type/feature The PR added a new feature or issue requested a new feature label Feb 27, 2019
@rdhabalia rdhabalia force-pushed the close_cnx branch 2 times, most recently from 868912c to 0b1a5db Compare March 5, 2019 20:13
@merlimat merlimat modified the milestones: 2.3.1, 2.4.0 Mar 7, 2019
@codelipenghui
Copy link
Contributor

@rdhabalia do we need this for 2.4.0? or shall move it to 2.5.0?

@sijie sijie modified the milestones: 2.4.0, 2.5.0 Jun 14, 2019
@sijie
Copy link
Member

sijie commented Jun 14, 2019

@rdhabalia I moved this pull request to 2.5.0 since it is idle for a while. If it is needed in 2.4.0, please move it back.

@aahmed-se
Copy link
Contributor

@rdhabalia can you rebase this.

@rdhabalia
Copy link
Contributor Author

rdhabalia commented Oct 24, 2019

@aahmed-se I have rebased the PR and it took a while as lot of changes have been merged since this PR was created.

@rdhabalia rdhabalia modified the milestones: 2.5.0, 2.4.2 Oct 24, 2019
@rdhabalia
Copy link
Contributor Author

rerun java8 tests

@rdhabalia
Copy link
Contributor Author

rerun cpp tests

@sijie sijie modified the milestones: 2.5.0, 2.6.0 Nov 25, 2019
@rdhabalia
Copy link
Contributor Author

@merlimat this is related to PIP-51.

@codelipenghui
Copy link
Contributor

@rdhabalia I moved this pull request to 2.7.0 since it is idle for a while. If it is needed in 2.6.0, please move it back.

@codelipenghui codelipenghui modified the milestones: 2.6.0, 2.7.0 May 19, 2020
@codelipenghui codelipenghui modified the milestones: 2.7.0, 2.8.0 Nov 4, 2020
@codelipenghui
Copy link
Contributor

@rdhabalia I moved this pull request to 2.9.0 since it is idle for a while. If it is needed in 2.8.0, please move it back

@codelipenghui codelipenghui modified the milestones: 2.8.0, 2.9.0 May 19, 2021
@rdhabalia
Copy link
Contributor Author

I think @merlimat have also implemented similar thing later on and didn't get chance to review this PR. So, I will close it. I guess we should review older PR rather creating duplicate one and closing old one.

@rdhabalia rdhabalia closed this Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/broker type/feature The PR added a new feature or issue requested a new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants