-
Notifications
You must be signed in to change notification settings - Fork 59
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
SVT: Enabling ARG SEC_SSO_PROVIDERS in Dockerfile causes conflicts with jakarta ee10 features #389
Comments
If I comment out the ARG SEC_SSO_PROVIDERS="oidc" line in my Dockerfile - and rebuild the image - then there are no conflicts at server startup. |
Setting SEC_SSO_PROVIDERS also enables the following features: appSecurity-2.0, socialLogin-1.0 This is added to the container at appSecurity-2.0 is causing conflict with the Jakarta EE10 features. So a workaround would be to add an empty file to replace it. Make sure to add the features, including socialLogin-1.0, to your server.xml.
FYI @rumanaHaque |
Thanks @leochr I was able to use this workaround, and successfully start my server without any conflicts. |
@leochr Do you know if this has already been fixed in the current Liberty builds? |
@rumanaHaque not yet, but we plan to add a flag to skip adding the SSO features. Let you know when it's added |
@leochr - Do you know if this defect has been fixed yet in the current Liberty builds? I am writing an Open Liberty blog which uses the same configuration, and was hoping I don't have to use the workaround as mentioned in this defect. Please let me know. Thanks. |
@rumanaHaque It's not in a release yet. We'll target 4Q to address this |
I am testing the OIDC in WebSphere Liberty Operator using this test case:
SVT: Test SSO with OIDC provider with WLO 1.1.0 using RH-SSO and new Jakarta-ee10 features
#276
As part of this test case, I have enabled these features in my server.xml
Also - I have these settings in my Dockerfile:
Having the ARG SEC_SSO_PROVIDERS="oidc" in my Dockerfile is causing conflicts when I start my server - with the following error:
The text was updated successfully, but these errors were encountered: