-
Notifications
You must be signed in to change notification settings - Fork 693
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
TOMEE-2247 - MicroProfile JWT Propagation 1.1 #173
Conversation
@radcortez where are we at? |
Hey @jeanouii, This was on hold, because @jgallimore picked this up and continue the work on his own branch here: Since he is done, I'm rebasing this with his branch and push an updated PR. Due to this: A few test cases in the TCK are failing. I believe this is an issue with the TCK itself. I think we can still test this if we implement our own tests with a separate app to expose the JWK endpoint. Me and @jgallimore discussed this on the ML and so I will be picking this up and hopefully complete the JWT 1.1 implementation work. |
So what do we do? |
@jeanouii this work should now be complete. I've sent an email about this to the ML. I think we can merge it. |
…war name and context root.
…ionScoped bean that loads data on application initialization.
…state all tests. Couple of failing JWT tests to go
…ods we use, so excluding it from the packaging here.
…e application start, but from the spec if the key is not present we need to fail with a Deployment Exception, so the key needs to be loaded eagerly.
… in new TCK version.
…ects application to be deployed to load the key, but key load is part of the deployment, so the key endpoint cannot be part of the app being tested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Executed the tests in the project and the bundled TCK project and they pass
No description provided.