[
https://issues.jboss.org/browse/WFLY-7159?page=com.atlassian.jira.plugin....
]
Darran Lofthouse resolved WFLY-7159.
------------------------------------
Fix Version/s: 11.0.0.Alpha1
Resolution: Rejected
I am rejecting this on the basis that it is too broad.
There are valid points in here so I recommend individual issues for the individual
concerns so we can address them all individually, not all issues raised automatically
point to refactoring a single subsystem.
Too complex Elytron Domain Model
--------------------------------
Key: WFLY-7159
URL:
https://issues.jboss.org/browse/WFLY-7159
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Fix For: 11.0.0.Alpha1
User experience with Elytron domain model is sub-optimal.
It's hard to define correctly complex attributes in the Elytron Subsystem
configuration. It's much simpler to write the CLI with primitive attributes instead.
Also the Management console is not able to generate forms for complex-types automatically.
1) Domain model of subsystem is too flat. Every resource (realms, mappers, factories ...)
is located at the base level of Elytron subsystem. Then it is hard to orientate in
subsystem since it does not have deeper structure.
Suggestion:
It can be structuralized similar as PicketBox subsystem. There could be some subresources
like realms, domains etc.
2) Elytron subsystem contains a lot of complex types which strongly complicate setting of
attributes for resources. It mainly affects
* {{add}} operation - there is insufficient support from CLI since tab button not
sufficiently works. It is also non-intuitive and error-prone when all setting is mixed to
one difficult command.
* {{write-attribute}} operation - using write-attribute for some values from complex
inner attribute is really hard - e.g. set particular value for some inner attribute of
complex object stored in list.
It is different aproach than most of other subsystems uses.
Suggestion:
Replace complex attributes with child resources.
This could be also discussed with UX team. Once this domain model will be released in
WildFly/EAP then it will be very hard to rewrite it do to backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)