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.

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

Update the Trader UI to work with global.auth=none #28

Open
jwalcorn opened this issue Jan 11, 2024 · 0 comments
Open

Update the Trader UI to work with global.auth=none #28

jwalcorn opened this issue Jan 11, 2024 · 0 comments

Comments

@jwalcorn
Copy link
Member

Right now, if you set global.auth=none in the CR yaml, that makes the downstream microservices use basic auth instead of a JWT. This is great for things curl -u stock:trader http://localhost:9080/broker, like during unit tests of a microservice, or other clients that don't want to deal with he complexities of constructing a JWT. However, the Trader UI fails, because it still tries sending a JWT, instead of basic auth credentials, in the auth http request header. Need to add basic auth support to Trader. Note this is slightly harder than it sounds, because the same servlet instance might need to handle different login IDs, so we can't just cache the id/pwd in the Login servlet. We'll have to do something like keeping a static HashMap of id (that I think we can get as the "principal" in a JAX-RS method?) to basic auth credential string (the encoded id:pwd thing), and use that on each request to Broker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant