[jboss-jira] [JBoss JIRA] (WFWIP-238) SSO support should have dual security

Jean Francois Denise (Jira) issues at jboss.org
Wed Oct 9 15:23:00 EDT 2019


     [ https://issues.jboss.org/browse/WFWIP-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean Francois Denise updated WFWIP-238:
---------------------------------------
    Description: 
Currently SSO configuration uses elytron, it is a change with prior configuration.
SSO support should detect if security subsystem is present and use it if SSO_FORCE_LEGACY_SECURITY=true. Elytron being used only if legacy security subsystem is not there or if SSO_FORCE_LEGACY_SECURITY=false (default value).

EAP CD18 will set SSO_FORCE_LEGACY_SECURITY=true

  was:
Currently SSO configuration uses elytron, it is a change with prior configuration.
SSO support should detect if security subsystem is present and use it. Elytron being used only if legacy security subsystem is not there.
This offers a backward compatible configuration.

Obviously this should be tuned in order to "modernize" the configuration by using elytron in all cases. That is made possible using the SSO_FORCE_ELYTRON_SECURITY=true.
That is what WildFly s2i is using by default.



> SSO support should have dual security
> -------------------------------------
>
>                 Key: WFWIP-238
>                 URL: https://issues.jboss.org/browse/WFWIP-238
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Jean Francois Denise
>            Assignee: Jean Francois Denise
>            Priority: Major
>
> Currently SSO configuration uses elytron, it is a change with prior configuration.
> SSO support should detect if security subsystem is present and use it if SSO_FORCE_LEGACY_SECURITY=true. Elytron being used only if legacy security subsystem is not there or if SSO_FORCE_LEGACY_SECURITY=false (default value).
> EAP CD18 will set SSO_FORCE_LEGACY_SECURITY=true



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list