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
[WFLY-17991] / [WFLY-17976] ee-security should depend on elytron and ensure the JACC policy is enabled by default. #16812
Conversation
Previously there was a choice between elytron and legacy security. As microprofile-jwt has a dependency on ee-security it no longer needs it's own elytron dependency.
…ation. This was not previously default as legacy security also provided this. When the ee-security layer is provisioned this policy should also be activated. The test case no longer needs to activate the policy once it is on by default.
---- | ||
[standalone@localhost:9990 /] reload | ||
---- | ||
specification. This policy provider is active default in the default |
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.
s/active default/active by default
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.
Thanks @darranl!
The policy is now a part of the default configuration.
@darranl Failures seem to be related. |
Hopefully that fix does it. One thing I have noticed I am sure we used to fail earlier but a lot of tests now are just ignoring set up failures and ploughing on so we end up with a cryptic test failure after the set up failed rather than an error reporting what went wrong during set up so we can jump straight to the point that needs a fix. |
Added ready-for-merge label as this has two reviews and CI is now green. |
https://issues.redhat.com/browse/WFLY-17991
https://issues.redhat.com/browse/WFLY-17976