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

[WFLY-17991] / [WFLY-17976] ee-security should depend on elytron and ensure the JACC policy is enabled by default. #16812

Merged
merged 5 commits into from May 10, 2023

Conversation

darranl
Copy link
Contributor

@darranl darranl commented May 5, 2023

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.
@github-actions github-actions bot added the deps-ok Dependencies have been checked, and there are no significant changes label May 5, 2023
@darranl darranl requested review from fjuma and Skyllarr May 5, 2023 15:14
----
[standalone@localhost:9990 /] reload
----
specification. This policy provider is active default in the default
Copy link
Contributor

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

Copy link
Contributor

@fjuma fjuma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @darranl!

@bstansberry
Copy link
Contributor

@darranl Failures seem to be related.

@darranl
Copy link
Contributor Author

darranl commented May 9, 2023

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.

@darranl darranl added the ready-for-merge Only for use by those with merge permissions! label May 10, 2023
@darranl
Copy link
Contributor Author

darranl commented May 10, 2023

Added ready-for-merge label as this has two reviews and CI is now green.

@jamezp jamezp merged commit cb58b0b into wildfly:main May 10, 2023
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deps-ok Dependencies have been checked, and there are no significant changes ready-for-merge Only for use by those with merge permissions!
Projects
None yet
4 participants