Farah Juma

Thanks @bstansberry, will do. I've added the hold label.

This PR is still active.

> There are 2 options that can be configured in galleon: `config-stability-level` and `package-stability-level` ( https://github.com/wildfly/wildfly-proposals/pull/555/files ) . From reading it seems to me that when `package-stability-level` option is configured...

> @luck3y @fjuma I'd prefer the WF TS not be aligned with Elytron over continuing to use this old Keycloak. Makes sense, we can go ahead and get this merged....

I'll need to take a closer look at this one to see what's happening. This was passing for me previously locally. The `microprofile-config.properties` file this test relies on already existed...

I see what's happening now. There were some changes that were also needed in the `scan-deployments` configuration in `testsuite/integration/micropfile/pom.xml` (similar to the updates that were made in https://github.com/wildfly/wildfly/pull/17153). However, even...

Removing the "hold" label now since the required Elytron component upgrade has been merged to Core. Once the Core component upgrade is in, CI should pass on this PR.

@rsearls Thanks for creating this PR for the subsystem bump. In general, it's good to include all the changes needed for the bump in addition to the xsd file. As...

@rsearls You'll want to introduce a wildfly-elytron-oidc-client_preview_4_0.xsd file that is a copy of the current wildfly-elytron-oidc-client_preview_3_0.xsd file without your new element added. Then in your changes for your RFE, you'll...

@rsearls Thanks for updating the commit message! Please also update the title as well to reference the community issue.