September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-782) Iteration count transformation: BSDUnixDESCryptPassword

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-782?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-782. ----------------------------- Resolution: Rejected Duplicates ELY-316 > Iteration count transformation: BSDUnixDESCryptPassword > ------------------------------------------------------- > > Key: ELY-782 > URL: https://issues.jboss.org/browse/ELY-782 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-780) Iteration count transformation: SunUnixMD5CryptPassword

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-780?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-780. ----------------------------- Resolution: Duplicate Issue Duplicates ELY-318 > Iteration count transformation: SunUnixMD5CryptPassword > ------------------------------------------------------- > > Key: ELY-780 > URL: https://issues.jboss.org/browse/ELY-780 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-781) Iteration count transformation: UnixSHACryptPassword

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-781?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-781. ----------------------------- Resolution: Duplicate Issue Duplicates ELY-319 > Iteration count transformation: UnixSHACryptPassword > ---------------------------------------------------- > > Key: ELY-781 > URL: https://issues.jboss.org/browse/ELY-781 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-341) PEM file format support

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-341?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-341. ----------------------------- Fix Version/s: 1.1.0.Beta10 (was: 1.2.0.Beta5) Resolution: Done We'll call this done for now. New JIRAs can be opened for additional support. > PEM file format support > ----------------------- > > Key: ELY-341 > URL: https://issues.jboss.org/browse/ELY-341 > Project: WildFly Elytron > Issue Type: Enhancement > Components: KeyStores > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.1.0.Beta10 > > > We should add support for PEM formats for formats including (but not limited to): > * X.509 Certificate > * CSRs > * CRLs > * RSA and DSA Public and Private Keys > * PKCS8 format Private Keys > * DH parameters > * ECDSA Public Key > * EC Private Key > * EC Parameters > This API could be consumed by various utilities or by custom credential storage implementations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-342) Add ability to acquire a PeerIdentityContext for a local SecurityDomain

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-342?page=com.atlassian.jira.plugin.sy... ] David Lloyd closed ELY-342. --------------------------- Resolution: Rejected This isn't actually needed. Can reopen if a new use case crops up. > Add ability to acquire a PeerIdentityContext for a local SecurityDomain > ----------------------------------------------------------------------- > > Key: ELY-342 > URL: https://issues.jboss.org/browse/ELY-342 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: David Lloyd > > Use cases for this feature: > * Local authentication (e.g. Remoting "local:" connections) > * Provide a possible way to allow JAAS APIs to authenticate to Elytron SecurityIdentity -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-446) Additional fields on SecurityIdentity

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-446?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-446. ----------------------------- Fix Version/s: 1.1.0.Beta10 Assignee: David Lloyd Resolution: Done > Additional fields on SecurityIdentity > ------------------------------------- > > Key: ELY-446 > URL: https://issues.jboss.org/browse/ELY-446 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta10 > > > The following useful properties could be added to SecurityIdentity: > * Identity creation time (the time when the identity itself is created, whether by login or by run-as) > * Authentication information, including: > ** Login timestamp (the time of the original authentication) > ** Login mechanism & kind (SASL/HTTP/TLS etc.) > ** Login protocol (HTTP/Remoting/etc.) incl. enclosing TLS information if any > * Authentication identity information, including: > ** Original authentication name > ** Authentication forwarding credential(s) > * Connection circumstances: > ** Peer and local address > ** Current invocation protocol -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-383) Update ServerAuthenticationContext to carry an identity from start to end

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-383?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-383. ----------------------------- Resolution: Done > Update ServerAuthenticationContext to carry an identity from start to end > ------------------------------------------------------------------------- > > Key: ELY-383 > URL: https://issues.jboss.org/browse/ELY-383 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: David Lloyd > Assignee: David Lloyd > Attachments: Blank Flowchart - ServerAuthenticationContext.png > > > The {{ServerAuthenticationContext}} should capture the identity in force for its domain when it is constructed. Any authorization attempt should always apply to the current identity - either the captured identity, or whatever the last successfully authorized identity was in the context. > The attached state diagram should accurately summarize how authorization identity flows through. Authentication identity is only available during the "NAME ASSIGNED" state; once authorization occurs, the authentication identity is no longer useful and is disposed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-496) Support for JAAS Subject inclusion in SecurityIdentity (via PeerIdentity)

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-496?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-496. ----------------------------- Resolution: Rejected I think it has become apparent that we don't actually need this capability. > Support for JAAS Subject inclusion in SecurityIdentity (via PeerIdentity) > ------------------------------------------------------------------------- > > Key: ELY-496 > URL: https://issues.jboss.org/browse/ELY-496 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > > We will probably need a way to configure a security domain to associate an legacy JAAS Subject to a SecurityIdentity. This would fit with the existing capabilities of associating a PeerIdentity to the SecurityIdentity, and transforming the SecurityIdentity. > However the way that PeerIdentity performs associations is with a before and after call. We need to support another mechanism that can use e.g. a function to wrap, because the only way to associate a Subject in JAAS is to create an AccessControlContext with a SubjectDomainCombiner, and to associate an AccessControlContext one must use doPrivileged. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-455) OAuth2 Credential Store

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-455?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-455: --------------------------------- Can this be closed? > OAuth2 Credential Store > ----------------------- > > Key: ELY-455 > URL: https://issues.jboss.org/browse/ELY-455 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Credential Store > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.2.0.Beta5 > > > Need an OAuth2 credential store which can acquire a cached OAuth2 token or instigate a new authentication. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-700) Fix AuthenticationClient comparison behavior

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-700?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-700. ----------------------------- Assignee: David Lloyd Resolution: Done > Fix AuthenticationClient comparison behavior > -------------------------------------------- > > Key: ELY-700 > URL: https://issues.jboss.org/browse/ELY-700 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > > The authentication client's comparison behavior is more or less banjaxed. It needs to be fixed, starting probably with killing off multi-valued configuration items. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 September 2017