May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4486) Support for multiple security realms - Failover

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4486?page=com.atlassian.jira.plugi... ] Farah Juma updated WFCORE-4486: ------------------------------- Fix Version/s: 11.0.0.Beta1 > Support for multiple security realms - Failover > ----------------------------------------------- > > Key: WFCORE-4486 > URL: https://issues.jboss.org/browse/WFCORE-4486 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Priority: Major > Labels: CD17-Deferred, EAP-CD19 > Fix For: 11.0.0.Beta1 > > > Our security realms are able to indicate unavailability by throwing a RealmUnavailableException > We should support fail over to an alternative realm. > A common request is fail over to a local file based realm if an LDAP or database server has gone down allowing administrators to retain access to the server. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4485) Support for multiple security realms - Distributed Identities

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4485?page=com.atlassian.jira.plugi... ] Farah Juma moved EAP7-1264 to WFCORE-4485: ------------------------------------------ Project: WildFly Core (was: EAP 7 Planning Pilot) Key: WFCORE-4485 (was: EAP7-1264) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Security (was: Security) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.3.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) Writer: (was: Chuck Copello) > Support for multiple security realms - Distributed Identities > ------------------------------------------------------------- > > Key: WFCORE-4485 > URL: https://issues.jboss.org/browse/WFCORE-4485 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Priority: Major > Labels: CD17-Deferred, EAP-CD19, Previous_RFE > Fix For: 11.0.0.Beta1 > > > By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list. > This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together. > Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged. > This RFE is not about fail over in the event of a realm being unavailable although it may be related. > This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4485) Support for multiple security realms - Distributed Identities

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4485?page=com.atlassian.jira.plugi... ] Farah Juma updated WFCORE-4485: ------------------------------- Fix Version/s: 11.0.0.Beta1 > Support for multiple security realms - Distributed Identities > ------------------------------------------------------------- > > Key: WFCORE-4485 > URL: https://issues.jboss.org/browse/WFCORE-4485 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Priority: Major > Labels: CD17-Deferred, EAP-CD19, Previous_RFE > Fix For: 11.0.0.Beta1 > > > By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list. > This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together. > Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged. > This RFE is not about fail over in the event of a realm being unavailable although it may be related. > This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-629) Enabled automatic encryption of passwords stored in configuration

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-629?page=com.atlassian.jira.plugin... ] Farah Juma updated WFCORE-629: ------------------------------ Fix Version/s: 11.0.0.Beta1 (was: 9.0.0.CR1) > Enabled automatic encryption of passwords stored in configuration > ----------------------------------------------------------------- > > Key: WFCORE-629 > URL: https://issues.jboss.org/browse/WFCORE-629 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Environment: Wildfly 9 > Reporter: Jason Shepherd > Assignee: Darran Lofthouse > Priority: Major > Fix For: 11.0.0.Beta1 > > > Currently encrypting passwords such as Datasource passwords can only be done 'after the fact'. You have to create the datasource first, then retrospectively store the password in the vault and dereference it in the configuration. > It would be great if could turn on automatic storage of passwords in the vault so that when you create a Datasource password, or add a resource adapter which specifies a remote resource password, those passwords were automatically added to the vault, and deferenced in the configuration file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4484) Support SSH authentication for Git persistence

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4484?page=com.atlassian.jira.plugi... ] Farah Juma updated WFCORE-4484: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 10.0.0.Beta1) > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: WFCORE-4484 > URL: https://issues.jboss.org/browse/WFCORE-4484 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: Farah Juma > Priority: Major > Labels: EAP-CD19 > Fix For: 11.0.0.Beta1 > > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4484) Support SSH authentication for Git persistence

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4484?page=com.atlassian.jira.plugi... ] Farah Juma moved EAP7-1263 to WFCORE-4484: ------------------------------------------ Project: WildFly Core (was: EAP 7 Planning Pilot) Key: WFCORE-4484 (was: EAP7-1263) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Management Security (was: Management) (was: Security) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.3.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) Affects Version/s: (was: 7.2.0.GA) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: WFCORE-4484 > URL: https://issues.jboss.org/browse/WFCORE-4484 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: Farah Juma > Priority: Major > Labels: EAP-CD19 > Fix For: 10.0.0.Beta1 > > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4484) Support SSH authentication for Git persistence

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4484?page=com.atlassian.jira.plugi... ] Farah Juma updated WFCORE-4484: ------------------------------- Fix Version/s: 10.0.0.Beta1 > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: WFCORE-4484 > URL: https://issues.jboss.org/browse/WFCORE-4484 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: Farah Juma > Priority: Major > Labels: EAP-CD19 > Fix For: 10.0.0.Beta1 > > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11868) Introduce Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-11868?page=com.atlassian.jira.plugin... ] Farah Juma updated WFLY-11868: ------------------------------ Fix Version/s: 19.0.0.Beta1 > Introduce Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11868 > URL: https://issues.jboss.org/browse/WFLY-11868 > Project: WildFly > Issue Type: Feature Request > Components: REST, Security > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > Labels: EAP-CD18 > Fix For: 19.0.0.Beta1 > > > This feature request is about making use of authentication configuration on the client side of the REST deployment. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4483) Add support for missing MP-JWT requirements

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4483?page=com.atlassian.jira.plugi... ] Farah Juma updated WFCORE-4483: ------------------------------- Fix Version/s: 10.0.0.Beta1 > Add support for missing MP-JWT requirements > ------------------------------------------- > > Key: WFCORE-4483 > URL: https://issues.jboss.org/browse/WFCORE-4483 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Priority: Major > Labels: EAP-CD18 > Fix For: 10.0.0.Beta1 > > > There are two main things that are currently missing: > * Support for injection of the currently authenticated caller as a {{JsonWebToken}} > * The {{java.security.Principal}} returned from {{javax.ws.rs.core.SecurityContext.getUserPrincipal()}} must be an instance of {{org.eclipse.microprofile.jwt.JsonWebToken}} > More details can be found [here|https://www.eclipse.org/community/eclipse_newsletter/2017/september/...]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4483) Add support for missing MP-JWT requirements

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4483?page=com.atlassian.jira.plugi... ] Farah Juma moved EAP7-1262 to WFCORE-4483: ------------------------------------------ Project: WildFly Core (was: EAP 7 Planning Pilot) Key: WFCORE-4483 (was: EAP7-1262) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Security (was: Security) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.3.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Add support for missing MP-JWT requirements > ------------------------------------------- > > Key: WFCORE-4483 > URL: https://issues.jboss.org/browse/WFCORE-4483 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Priority: Major > Labels: EAP-CD18 > > There are two main things that are currently missing: > * Support for injection of the currently authenticated caller as a {{JsonWebToken}} > * The {{java.security.Principal}} returned from {{javax.ws.rs.core.SecurityContext.getUserPrincipal()}} must be an instance of {{org.eclipse.microprofile.jwt.JsonWebToken}} > More details can be found [here|https://www.eclipse.org/community/eclipse_newsletter/2017/september/...]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 May 2019