February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-861) Role assignment not possible for "anonymous" identity

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-861?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-861: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > Role assignment not possible for "anonymous" identity > ----------------------------------------------------- > > Key: ELY-861 > URL: https://issues.jboss.org/browse/ELY-861 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta25 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-854) OAuth2SaslServer is missing authorization and mechanism information

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-854?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-854: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > OAuth2SaslServer is missing authorization and mechanism information > ------------------------------------------------------------------- > > Key: ELY-854 > URL: https://issues.jboss.org/browse/ELY-854 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.1.0.Beta18 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta25 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-853) OAuth2CredentialSource must handle BearerTokenCredential only

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-853?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-853: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > OAuth2CredentialSource must handle BearerTokenCredential only > ------------------------------------------------------------- > > Key: ELY-853 > URL: https://issues.jboss.org/browse/ELY-853 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta18 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta25 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-849?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-849: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > Rename setMechanismProperties to setSaslMechanismProperties > ----------------------------------------------------------- > > Key: ELY-849 > URL: https://issues.jboss.org/browse/ELY-849 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta25 > > > If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties. > We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-838) Ability to obtain SecurityIdentity without requiring LoginPermission

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-838?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-838: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > Ability to obtain SecurityIdentity without requiring LoginPermission > -------------------------------------------------------------------- > > Key: ELY-838 > URL: https://issues.jboss.org/browse/ELY-838 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta25 > > > Integrations such as the batch subsystem within WildFly have the requirement to re-create a previous SecurityIdentity by name using their referenced SecurityDomain, however as this identity may have been inflowed the LoginPermission can not be assumed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-940) key-store-ssl-certificate -> key-store-clear-password is wrapping parsing inside the Supplier

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-940?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-940: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > key-store-ssl-certificate -> key-store-clear-password is wrapping parsing inside the Supplier > --------------------------------------------------------------------------------------------- > > Key: ELY-940 > URL: https://issues.jboss.org/browse/ELY-940 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta25 > > > This means we get errors like this where the parser is accessed after parsing should have finished: - > {{[disconnected /] connect > java.lang.IllegalStateException: Current event not START_ELEMENT > at com.ctc.wstx.sr.BasicStreamReader.getAttributeCount(BasicStreamReader.java:584) > at org.wildfly.client.config.BasicXMLStreamReader.getAttributeCount(BasicXMLStreamReader.java:191) > at org.wildfly.client.config.AbstractDelegatingXMLStreamReader.getAttributeCount(AbstractDelegatingXMLStreamReader.java:148) > at org.wildfly.client.config.AbstractDelegatingXMLStreamReader.getAttributeCount(AbstractDelegatingXMLStreamReader.java:148) > at org.wildfly.security.auth.client.ElytronXmlParser.parseClearPassword(ElytronXmlParser.java:1864) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$43(ElytronXmlParser.java:1270) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$44(ElytronXmlParser.java:1286) > at org.wildfly.security.auth.client.ElytronXmlParser$PrivateKeyKeyStoreEntryCredentialFactory.get(ElytronXmlParser.java:2232) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$5(ElytronXmlParser.java:434) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$6(ElytronXmlParser.java:457) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$8(ElytronXmlParser.java:493) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:292) > }} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-939) We need to be able to support standard KeyManager instances

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-939?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-939: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > We need to be able to support standard KeyManager instances > ----------------------------------------------------------- > > Key: ELY-939 > URL: https://issues.jboss.org/browse/ELY-939 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta25 > > > When using PKCS#11 we should not assume we can manipulate the private keys etc.. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-938) KeyStore in authentication client should not mandate an input source

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-938?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-938: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > KeyStore in authentication client should not mandate an input source > -------------------------------------------------------------------- > > Key: ELY-938 > URL: https://issues.jboss.org/browse/ELY-938 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta25 > > > Some keystores such as PKCS#11 are initialised without an InputStream. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-937) SSLContext in authentication client has no trust configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-937?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-937: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > SSLContext in authentication client has no trust configuration > -------------------------------------------------------------- > > Key: ELY-937 > URL: https://issues.jboss.org/browse/ELY-937 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta25 > > > Currently it requires on the system default so it is not possible to configure trusted certificate authorities. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-936) Complete equivalent of CLIENT_CERT authentication for SASL

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-936?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-936: --------------------------------- Fix Version/s: 1.1.0.Beta25 (was: 1.1.0.Beta24) > Complete equivalent of CLIENT_CERT authentication for SASL > ---------------------------------------------------------- > > Key: ELY-936 > URL: https://issues.jboss.org/browse/ELY-936 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta25 > > > This will likely extend outside of Elytron but track it here first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

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 February 2017