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

Allow passing the bearer token to the broker directly #4

Closed
lavocatt opened this issue Dec 18, 2024 · 0 comments
Closed

Allow passing the bearer token to the broker directly #4

lavocatt opened this issue Dec 18, 2024 · 0 comments
Assignees
@lavocatt

Comments

@lavocatt
Copy link
Collaborator

In order to support authentication on OpenShift allow passing a bearer token that was passed from the client to the broker.
Let the broker do the authentication.
@lavocatt lavocatt self-assigned this Dec 18, 2024
lavocatt added a commit to lavocatt/activemq-artemis-jolokia-api-server that referenced this issue Dec 18, 2024
@lavocatt
[arkmq-org#4] no login, token transferred to the broker
34f0652 
The jolokia api server is now in a mode where it doesn't perform
any login verification and just forward the Bearer token to the broker.
The user needs to provide a targetEndpoint and a Bearer token on every
request except api-info.

Based on @gaohoward's work there: artemiscloud#23
lavocatt added a commit to lavocatt/activemq-artemis-jolokia-api-server that referenced this issue Dec 18, 2024
@lavocatt
[arkmq-org#4] no login, token transferred to the broker
43e0075 
The jolokia api server is now in a mode where it doesn't perform
any login verification and just forward the Bearer token to the broker.
The user needs to provide a targetEndpoint and a Bearer token on every
request except api-info.

Based on @gaohoward's work there: artemiscloud#23
lavocatt added a commit to lavocatt/activemq-artemis-jolokia-api-server that referenced this issue Dec 18, 2024
@lavocatt
[arkmq-org#4] no login, token transferred to the broker
91c3c94 
The jolokia api server is now in a mode where it doesn't perform
any login verification and just forward the Bearer token to the broker.
The user needs to provide a targetEndpoint and a Bearer token on every
request except api-info.

Based on @gaohoward's work there: artemiscloud#23
lavocatt added a commit to lavocatt/activemq-artemis-jolokia-api-server that referenced this issue Dec 18, 2024
@lavocatt
[arkmq-org#4] no login, token transferred to the broker
30406c5 
The jolokia api server is now in a mode where it doesn't perform
any login verification and just forward the Bearer token to the broker.
The user needs to provide a targetEndpoint and a Bearer token on every
request except api-info.

Based on @gaohoward's work there: artemiscloud#23
lavocatt added a commit to lavocatt/activemq-artemis-jolokia-api-server that referenced this issue Dec 19, 2024
@lavocatt
[arkmq-org#4] no login, token transferred to the broker
142240d 
The jolokia api server is now in a mode where it doesn't perform
any login verification and just forward the Bearer token to the broker.
The user needs to provide a targetEndpoint and a Bearer token on every
request except api-info.

Based on @gaohoward's work there: artemiscloud#23
lavocatt added a commit that referenced this issue Jan 8, 2025
@lavocatt
[#4] no login, token transferred to the broker
58e4f7e 
The jolokia api server is now in a mode where it doesn't perform
any login verification and just forward the Bearer token to the broker.
The user needs to provide a targetEndpoint and a Bearer token on every
request except api-info.

Based on @gaohoward's work there: artemiscloud#23
@lavocatt lavocatt closed this as completed Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lavocatt lavocatt

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lavocatt