July 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-200) Add a set of standard HTTP authentication mechanisms

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-200?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-200: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Add a set of standard HTTP authentication mechanisms > ---------------------------------------------------- > > Key: ELY-200 > URL: https://issues.jboss.org/browse/ELY-200 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > i.e. BASIC, DIGEST, CLENT_CERT, FORM (Generic), SPNEGO -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-199) HTTP Authentication Mechanism API / SPI

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-199?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-199: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > HTTP Authentication Mechanism API / SPI > --------------------------------------- > > Key: ELY-199 > URL: https://issues.jboss.org/browse/ELY-199 > Project: WildFly Elytron > Issue Type: Sub-task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > A web server agnostic HTTP authentication mechanism framework. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-178) Domain to domain identity propagation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-178?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-178: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Domain to domain identity propagation > ------------------------------------- > > Key: ELY-178 > URL: https://issues.jboss.org/browse/ELY-178 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Realms > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > At the lowest level a users identity is associated with a single SecurityRealm, two accounts that authenticated against different realms will never be considered equal. > However on top of this we have the security domains, a security domain amongst other things is an aggregation of realms. Incoming server connections and also applications can be associated with a security domain. However we still have the following two scenarios of a call to complete the consideration for: - > Connection -> Deployment > Deployment -> Deployment > In the first case the connection may be associated with a security domain with a large set of realms, however the deployment may be associated with a smaller set of realms. In the case that the realm is in both of these domains we need the identity to be able to automatically propagate. > Same for deployment to deployment calls, if there is a common realm the identity should propagate. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-176) HTTP AuthenticationMechanism Factory and Provider registration.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-176?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-176: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > HTTP AuthenticationMechanism Factory and Provider registration. > --------------------------------------------------------------- > > Key: ELY-176 > URL: https://issues.jboss.org/browse/ELY-176 > Project: WildFly Elytron > Issue Type: Sub-task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > We are for now going to need to be Undertow specific unless we come up with a solution for a generic API/SPI to be implemented by HTTP mechanisms that also gives access to the request / response. > This task is to define a factory SPI and to make all known HTTP mechanisms available using this SPI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-174) HTTP Authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-174?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-174: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > HTTP Authentication > ------------------- > > Key: ELY-174 > URL: https://issues.jboss.org/browse/ELY-174 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > So far we have been very focussed on the SASL side of authentication, similar capabilities are required for HTTP - the difference being that SASL is based on selecting one at a time, HTTP all mechanisms need to run concurrently. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-159) Discovery of available algorithms for credential types

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-159?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-159: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Discovery of available algorithms for credential types > ------------------------------------------------------ > > Key: ELY-159 > URL: https://issues.jboss.org/browse/ELY-159 > Project: WildFly Elytron > Issue Type: Sub-task > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > The overall purpose of the getCredentialSupport calls is so that we can discover information about the supported credentials as authentication mechanisms are offered - the algorithm for the digest is just as important as knowing the general type. > May just be a part of ELY-151 or may be something in addition. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-155) Condense Message IDs

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-155?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-155: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Condense Message IDs > -------------------- > > Key: ELY-155 > URL: https://issues.jboss.org/browse/ELY-155 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.0.0.Alpha4 > > > This is a task to complete at the point of tagging, condense the message IDs to close any gaps in the numbering. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-250) Release WildFly Elytron 1.0.0.Alpha3

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-250?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-250. ---------------------------------- Resolution: Done > Release WildFly Elytron 1.0.0.Alpha3 > ------------------------------------ > > Key: ELY-250 > URL: https://issues.jboss.org/browse/ELY-250 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-245) Domain / Realm Dry Runs

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-245?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-245: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > Domain / Realm Dry Runs > ----------------------- > > Key: ELY-245 > URL: https://issues.jboss.org/browse/ELY-245 > Project: WildFly Elytron > Issue Type: Task > Components: Realms > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha4 > > > Can we provide some utility to help 'dry run' the process of taking a name through the name rewriter, realm mappers etc... > Generally someting to allow a user to test their config using management ops. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-232) AuthorizeCallback shall be last

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-232?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-232: --------------------------------- Fix Version/s: 1.0.0.Alpha4 (was: 1.0.0.Alpha3) > AuthorizeCallback shall be last > ------------------------------- > > Key: ELY-232 > URL: https://issues.jboss.org/browse/ELY-232 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: David Lloyd > Fix For: 1.0.0.Alpha4 > > > Go through each SASL server mechanism and ensure that AuthorizeCallback is checked last (after credential/password verification, user name assignment, realm checks, etc.). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2015