Skip to content
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

Jump to bottom

Add support for OAuth 2 authentication #626

Closed
acogoluegnes opened this issue Sep 12, 2019 · 1 comment
Closed

Add support for OAuth 2 authentication #626

acogoluegnes opened this issue Sep 12, 2019 · 1 comment
Assignees
@acogoluegnes
Labels
effort-medium enhancement
Milestone
5.8.0

Comments

@acogoluegnes
Copy link
Contributor

RabbitMQ 3.8 ships with OAuth 2 support. The client should provide utility to retrieve JWT tokens and to refresh them when appropriate.
@acogoluegnes acogoluegnes added this to the 5.8.0 milestone Sep 12, 2019
@acogoluegnes acogoluegnes self-assigned this Sep 12, 2019
@acogoluegnes
Copy link
Contributor Author

Implemented in

4251459
5752e55
6277348
97c8700
443a589
136b3ea
7b50067
77951bc
1c7b21c
7dc7170
09f5320
a9e8e73

acogoluegnes added a commit that referenced this issue Sep 16, 2019
@acogoluegnes
Do not depend on generated classes for update-secret extension
e3c662e 
Some CI testing jobs are using the 3.7 branch of codegen, which does not contain
the update-secret extension. The Java client then cannot be built
because it requires some generated code for the extension.

This commit adds the code to handle update-secret and thus
makes the generated code not necessary. This is just a workaround for
these testing jobs to succeed, it does not change the handling of the
update-secret extension in the client.

[#167029587]

References #626
@acogoluegnes acogoluegnes mentioned this issue Sep 16, 2019
Merged
acogoluegnes added a commit that referenced this issue Sep 17, 2019
@acogoluegnes
Do not depend on generated classes for update-secret extension
96718db 
Some CI testing jobs are using the 3.7 branch of codegen, which does not contain
the update-secret extension. The Java client then cannot be built
because it requires some generated code for the extension.

This commit adds the code to handle update-secret and thus
makes the generated code not necessary. This is just a workaround for
these testing jobs to succeed, it does not change the handling of the
update-secret extension in the client.

[#167029587]

References #626

(cherry picked from commit e3c662e)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@acogoluegnes acogoluegnes

Labels
effort-medium enhancement
Projects
None yet
Milestone
5.8.0
Development

No branches or pull requests
1 participant
@acogoluegnes