[JBoss JIRA] (WFLY-7066) Wrong description of simple-regex-realm-mapper / mapped-regex-realm-mapper in model
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7066?page=com.atlassian.jira.plugin.... ]
Martin Choma moved JBEAP-5908 to WFLY-7066:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7066 (was: JBEAP-5908)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR4)
> Wrong description of simple-regex-realm-mapper / mapped-regex-realm-mapper in model
> -----------------------------------------------------------------------------------
>
> Key: WFLY-7066
> URL: https://issues.jboss.org/browse/WFLY-7066
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
>
> In output of {noformat}/subsystem=elytron:read-resource-description(recursive=true){noformat} , there is wrong description of simple-regex-realm-mapper / mapped-regex-realm-mapper _"Definition of a custom RealmMapper"_ , what is probably copied from custom-realm-mapper.
> In XSD, there is more proper
> * mapped-regex-realm-mapper: _"A RealmMapper implementaion that first uses a regular expression to extract the realm name, this is then converted using the configured mapping of realm names."_
> * simple-regex-realm-mapper: _"A simple RealmMapper definition that attempts to extract the realm name using the capture group from the regular expression, if that does not provide a match then the delegate RealmMapper is used instead."_
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7065) Wrong description of logical-role-mapper in model
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7065?page=com.atlassian.jira.plugin.... ]
Martin Choma moved JBEAP-5905 to WFLY-7065:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7065 (was: JBEAP-5905)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR4)
> Wrong description of logical-role-mapper in model
> -------------------------------------------------
>
> Key: WFLY-7065
> URL: https://issues.jboss.org/browse/WFLY-7065
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
>
> In output of
> {noformat}
> /subsystem=elytron:read-resource-description(recursive=true)
> {noformat}
> , there is wrong description of logical-role-mapper _A role mapper definition where a constant set of roles is always returned._ , what is probably copied from constant-role-mapper.
> In XSD, there is more proper description _A RoleMapper definition for a RoleMapper that performs a logical operation using two refereced RoleMappers._
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (SECURITY-955) Regression in parsing username in LdapExtLoginModule
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/SECURITY-955?page=com.atlassian.jira.plug... ]
Ondrej Lukas updated SECURITY-955:
----------------------------------
Affects Version/s: PicketBox_5_0_0.Alpha3
> Regression in parsing username in LdapExtLoginModule
> ----------------------------------------------------
>
> Key: SECURITY-955
> URL: https://issues.jboss.org/browse/SECURITY-955
> Project: PicketBox
> Issue Type: Bug
> Affects Versions: PicketBox_5_0_0.Alpha3
> Reporter: Ondrej Lukas
> Assignee: Stefan Guilhen
> Priority: Blocker
>
> In case when customers using LdapExtLoginModule with option parseUsername=true but without option usernameBeginString (i.e. usernameBeginString=null) then all users cannot be successfully authenticated into application. Authentication failure is caused by hidden internal NPE.
> It is the same issue as was reported in [1], but fix is missing in current EAP 7.1 version of PicketBox (5.0.0.Alpha3).
> We request blocker flag because:
> * Valid configuration which works for 7.0.x becomes invalid after migration to 7.1.0
> * All users cannot authenticate to application despite of valid EAP configuration
> * Authetication failure caused by NPE is logged to server log
> Thrown NPE:
> {code}
> java.lang.NullPointerException
> at org.jboss.security.auth.spi.LdapExtLoginModule.getUsername(LdapExtLoginModule.java:963)
> at org.jboss.security.auth.spi.LdapExtLoginModule.validatePassword(LdapExtLoginModule.java:342)
> at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:283)
> {code}
> [1] https://issues.jboss.org/browse/JBEAP-364?focusedCommentId=13160168&page=...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (SECURITY-955) Regression in parsing username in LdapExtLoginModule
by Ondrej Lukas (JIRA)
Ondrej Lukas created SECURITY-955:
-------------------------------------
Summary: Regression in parsing username in LdapExtLoginModule
Key: SECURITY-955
URL: https://issues.jboss.org/browse/SECURITY-955
Project: PicketBox
Issue Type: Bug
Reporter: Ondrej Lukas
Assignee: Stefan Guilhen
Priority: Blocker
In case when customers using LdapExtLoginModule with option parseUsername=true but without option usernameBeginString (i.e. usernameBeginString=null) then all users cannot be successfully authenticated into application. Authentication failure is caused by hidden internal NPE.
It is the same issue as was reported in [1], but fix is missing in current EAP 7.1 version of PicketBox (5.0.0.Alpha3).
We request blocker flag because:
* Valid configuration which works for 7.0.x becomes invalid after migration to 7.1.0
* All users cannot authenticate to application despite of valid EAP configuration
* Authetication failure caused by NPE is logged to server log
Thrown NPE:
{code}
java.lang.NullPointerException
at org.jboss.security.auth.spi.LdapExtLoginModule.getUsername(LdapExtLoginModule.java:963)
at org.jboss.security.auth.spi.LdapExtLoginModule.validatePassword(LdapExtLoginModule.java:342)
at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:283)
{code}
[1] https://issues.jboss.org/browse/JBEAP-364?focusedCommentId=13160168&page=...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7064) IdentityLoginModuleTestCase is incorrect
by Stuart Douglas (JIRA)
Stuart Douglas created WFLY-7064:
------------------------------------
Summary: IdentityLoginModuleTestCase is incorrect
Key: WFLY-7064
URL: https://issues.jboss.org/browse/WFLY-7064
Project: WildFly
Issue Type: Bug
Reporter: Stuart Douglas
Assignee: Stuart Douglas
This test assumes that the security path of '/' will be a wildcard match, while in reality it should only match the root url. This test only passed due to UNDERTOW-805
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7063) IdentityLoginModuleTestCase is incorrect
by Stuart Douglas (JIRA)
Stuart Douglas created WFLY-7063:
------------------------------------
Summary: IdentityLoginModuleTestCase is incorrect
Key: WFLY-7063
URL: https://issues.jboss.org/browse/WFLY-7063
Project: WildFly
Issue Type: Bug
Reporter: Stuart Douglas
Assignee: Stuart Douglas
This test assumes that the security path of '/' will be a wildcard match, while in reality it should only match the root url. This test only passed due to UNDERTOW-805
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months