[jboss-jira] [JBoss JIRA] (WFCORE-3367) Add note to elytron attributes that affects EAP configuration globally
Jan Kalina (JIRA)
issues at jboss.org
Thu Dec 7 12:30:00 EST 2017
[ https://issues.jboss.org/browse/WFCORE-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Kalina closed WFCORE-3367.
------------------------------
Resolution: Rejected
As this change as requested more discussion and considerations then appropriate such minor improvement, rejected.
> Add note to elytron attributes that affects EAP configuration globally
> ----------------------------------------------------------------------
>
> Key: WFCORE-3367
> URL: https://issues.jboss.org/browse/WFCORE-3367
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 3.0.6.Final
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Minor
>
> There are some attributes in elytron subsystem which have global effect on EAP server state even in case elytron security is not utilized in any way. Those are (at least):
> * disallowed-providers
> * final-providers
> * initial-providers
> We should put some note in description of those attributes that they have global effect on EAP server and take effect even in cases elytron security is not utilized anyhow. Reason is that it might be a little confusing for customers to find and configure these attributes in elytron subsystem even in case they use just legacy security-realm. One would expect that when something is configured in elytron subsystem it has not take effect unless explicitely referenced or used (because we still have also legacy security-realm based security). It is not a perfect state/UX but as Elytron is supposed to become a common and only place for server security configuration it is understandable that all new security related things are being put there.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list