[
https://issues.jboss.org/browse/WFLY-11083?page=com.atlassian.jira.plugin...
]
Jan Kalina moved ELY-1685 to WFLY-11083:
----------------------------------------
Project: WildFly (was: WildFly Elytron)
Key: WFLY-11083 (was: ELY-1685)
Component/s: Documentation
(was: XML)
Fix Version/s: (was: 1.1.0.Beta49)
Incorrectly named attribute match-user in authentication-context in
Elytron subsystem
-------------------------------------------------------------------------------------
Key: WFLY-11083
URL:
https://issues.jboss.org/browse/WFLY-11083
Project: WildFly
Issue Type: Bug
Components: Documentation
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Critical
Labels: user_experience
Rule matcher {{match-user}} in authentication-context in Elytron subsystem internally
uses {{org.wildfly.security.auth.client.MatchUserRule}}. This matcher works based on
passed userinfo. However naming of {{match-user}} in Elytron subsystem indicates that just
user part of userinfo should be used in matching.
Also description in CLI is not correct, it says: _The user to match against._
It means one of following should be changed:
* name of {{match-user}}
* functionality of {{MatchUserRule}}
Since Elytron client configuration file includes for the same matcher with name
{{match-userinfo}} then I suggest to rename attribute {{match-user}} in
{{authentication-context}} in Elytron subsystem to {{match-userinfo}} and improve
description in CLI and XSD.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)