[
https://issues.jboss.org/browse/WFWIP-238?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on WFWIP-238:
----------------------------------------
Wouldn't it be better to have the configuration option the other way round i.e.
SSO_FORCE_LEGACY_SECURITY=true with this present by default?
In the future once legacy security is removed the only real step required will be removing
this option.
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. 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.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)