June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-968) SI.createRunAsIdentity ignores authorize flag

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-968?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-968. ----------------------------- Fix Version/s: 1.1.0.Beta27 Resolution: Done > SI.createRunAsIdentity ignores authorize flag > --------------------------------------------- > > Key: ELY-968 > URL: https://issues.jboss.org/browse/ELY-968 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI, Authentication Server > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta27 > > > The parameter is ignored, and false is always used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1052) For the wrapped SSLEngine and SSLSockets allow further restriction of cipher suites.

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1052?page=com.atlassian.jira.plugin.s... ] David Lloyd updated ELY-1052: ----------------------------- Comment: was deleted (was: Related to ELY-1179) > For the wrapped SSLEngine and SSLSockets allow further restriction of cipher suites. > ------------------------------------------------------------------------------------ > > Key: ELY-1052 > URL: https://issues.jboss.org/browse/ELY-1052 > Project: WildFly Elytron > Issue Type: Enhancement > Components: SSL > Reporter: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > We should allow further configuration where this configuration leads to a union of centrally enabled cipher suites with API specified cipher suites. > i.e. an administrator can centrally define the acceptable cipher suites but utilities using the APIs can restrict this further. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1052) For the wrapped SSLEngine and SSLSockets allow further restriction of cipher suites.

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1052?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1052: ---------------------------------- Related to ELY-1179 > For the wrapped SSLEngine and SSLSockets allow further restriction of cipher suites. > ------------------------------------------------------------------------------------ > > Key: ELY-1052 > URL: https://issues.jboss.org/browse/ELY-1052 > Project: WildFly Elytron > Issue Type: Enhancement > Components: SSL > Reporter: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > We should allow further configuration where this configuration leads to a union of centrally enabled cipher suites with API specified cipher suites. > i.e. an administrator can centrally define the acceptable cipher suites but utilities using the APIs can restrict this further. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1064) Deprecate "purpose" match criteria and parameter

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1064?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved ELY-1064. ------------------------------ Fix Version/s: 1.1.0.Beta51 Resolution: Done Duplicated by ELY-1213 > Deprecate "purpose" match criteria and parameter > ------------------------------------------------ > > Key: ELY-1064 > URL: https://issues.jboss.org/browse/ELY-1064 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: David Lloyd > Fix For: 1.1.0.Beta51 > > > The "purpose" property was a mistake; it will not be used by any of the Elytron-aware client libraries. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1094) Release WildFly Elytron 1.1.0.Beta38

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1094?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved ELY-1094. ------------------------------ Fix Version/s: 1.1.0.Beta38 (was: 1.1.0.Beta53) Resolution: Done > Release WildFly Elytron 1.1.0.Beta38 > ------------------------------------ > > Key: ELY-1094 > URL: https://issues.jboss.org/browse/ELY-1094 > Project: WildFly Elytron > Issue Type: Release > Reporter: Peter Skopek > Assignee: Peter Skopek > Fix For: 1.1.0.Beta38 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8908) PicketBoxBasedIdentity.exists() should check if a valid JAAS Subject exists instead of always returning true

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/WFLY-8908?page=com.atlassian.jira.plugin.... ] Stefan Guilhen updated WFLY-8908: --------------------------------- Description: The RealmIdentity.exists() method should be used to verify if a valid identity exists before an attempt to call other non-authentication methods - e.g. getAuthorizationIdentity() - is made. The PicketBoxBasedIdentity implementation in the SecurityDomainContextRealm is erroneously returning true when in fact it should be checking if a valid Subject was established as part of a previous JAAS authentication. The getAuthorizationIdentity() method can then simply throw an Exception if it is called without a valid JAAS Subject in place. Client code should check the result of the exists() method before attempting to get an AuthorizationIdentity so any code invoking getAuthorizationIdentity() without checking first if a valid identity exists should fail. > PicketBoxBasedIdentity.exists() should check if a valid JAAS Subject exists instead of always returning true > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-8908 > URL: https://issues.jboss.org/browse/WFLY-8908 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > > The RealmIdentity.exists() method should be used to verify if a valid identity exists before an attempt to call other non-authentication methods - e.g. getAuthorizationIdentity() - is made. > The PicketBoxBasedIdentity implementation in the SecurityDomainContextRealm is erroneously returning true when in fact it should be checking if a valid Subject was established as part of a previous JAAS authentication. > The getAuthorizationIdentity() method can then simply throw an Exception if it is called without a valid JAAS Subject in place. Client code should check the result of the exists() method before attempting to get an AuthorizationIdentity so any code invoking getAuthorizationIdentity() without checking first if a valid identity exists should fail. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8908) PicketBoxBasedIdentity.exists() should check if a valid JAAS Subject exists instead of always returning true

by Stefan Guilhen (JIRA)

Stefan Guilhen created WFLY-8908: ------------------------------------ Summary: PicketBoxBasedIdentity.exists() should check if a valid JAAS Subject exists instead of always returning true Key: WFLY-8908 URL: https://issues.jboss.org/browse/WFLY-8908 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 11.0.0.Alpha1 Reporter: Stefan Guilhen Assignee: Stefan Guilhen -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1100) Configured set-protocol in Elytron Client configuration file is not used

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1100?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved ELY-1100. ------------------------------ Resolution: Rejected This one was actually a Remoting bug, REM3-270. > Configured set-protocol in Elytron Client configuration file is not used > ------------------------------------------------------------------------ > > Key: ELY-1100 > URL: https://issues.jboss.org/browse/ELY-1100 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta34 > Reporter: Ondrej Lukas > Assignee: David Lloyd > Priority: Blocker > > When some configuration in Elytron Client configuration file uses set-protocol then value of this element is not used for outgoing connection. Elements set-host and set-port are used correctly. > Following authentication configuration part of wildfly-config.xml should use URL {{remote+http://localhost:9990}} for outgoing connection, but protocol {{remote+http}} from {{set-protocol}} is not used: > {code} > <authentication-configurations> > <configuration name="auth-config"> > <set-user-name name="user"/> > <set-protocol name="remote+http"/> > <set-host name="localhost"/> > <set-port number="9990"/> > <credentials> > <clear-password password="password"/> > </credentials> > </configuration> > </authentication-configurations> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1102) Provide accessors in AuthenticationContextConfigurationClient to read the configured protocol

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1102?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved ELY-1102. ------------------------------ Fix Version/s: 1.1.0.Beta40 (was: 1.1.0.Beta53) Resolution: Done > Provide accessors in AuthenticationContextConfigurationClient to read the configured protocol > --------------------------------------------------------------------------------------------- > > Key: ELY-1102 > URL: https://issues.jboss.org/browse/ELY-1102 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta40 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1109) Resolve expressions in wildfly-config.xml Elytron section

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1109?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved ELY-1109. ------------------------------ Fix Version/s: 1.1.0.Beta40 (was: 1.1.0.Beta53) Resolution: Done > Resolve expressions in wildfly-config.xml Elytron section > --------------------------------------------------------- > > Key: ELY-1109 > URL: https://issues.jboss.org/browse/ELY-1109 > Project: WildFly Elytron > Issue Type: Enhancement > Components: XML > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta40 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2017