July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7701) All subsystems referencing a SecurityDomain should optionally support a role mapping category

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7701?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7701: -------------------------------------- Assignee: (was: Darran Lofthouse) > All subsystems referencing a SecurityDomain should optionally support a role mapping category > --------------------------------------------------------------------------------------------- > > Key: WFLY-7701 > URL: https://issues.jboss.org/browse/WFLY-7701 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Priority: Minor > > The role mapping category allows for a common security domain to be used with different role mapping definitions. Also a configuration option should be provided to decide if it should drop to default. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-7639) Missing XSD for wildfly-config.xml

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7639?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-7639. ------------------------------------ Resolution: Done > Missing XSD for wildfly-config.xml > ---------------------------------- > > Key: WFLY-7639 > URL: https://issues.jboss.org/browse/WFLY-7639 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 11.0.0.Beta1 > > > There is a new client configuration required in `wildfly-config.xml` (more in JBEAP-7104), but the `docs/schema` folder doesn't contain its XSD (schema definition). > We have to provide one with a sufficient description of the elements and attributes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8061) Support role mapping from jboss deployment descriptors in undertow subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8061?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-8061: -------------------------------------- Assignee: (was: Darran Lofthouse) > Support role mapping from jboss deployment descriptors in undertow subsystem > ---------------------------------------------------------------------------- > > Key: WFLY-8061 > URL: https://issues.jboss.org/browse/WFLY-8061 > Project: WildFly > Issue Type: Enhancement > Components: Security, Web (Undertow) > Reporter: Pedro Igor > > Currently, role mapping from jboss-web.xml and jboss-app.xml are not taken into consideration when mapping roles for an identity in Elytron. > This already being done by ejb subsystem, but we lack in web/undertow subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-7986) Add some exclusions to the 'org.wildfly.extension.elytron' module.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7986?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-7986. ------------------------------------ Resolution: Out of Date > Add some exclusions to the 'org.wildfly.extension.elytron' module. > ------------------------------------------------------------------ > > Key: WFLY-7986 > URL: https://issues.jboss.org/browse/WFLY-7986 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 11.0.0.Beta1 > > > Likely to be something like: - > bq. <exports> > bq. <exclude path="org/wildfly/extension/elytron/ElytronExtension"/> > bq. <exclude path="org/wildfly/extension/elytron/_private"/> > bq. <exclude path="org/wildfly/extension/elytron/capabilities"/> > bq. </exports> > Although capabilities also needs to be double checked, this may be moved and hidden using standard Java visibility modifiers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8245) AuthenticationContext should not be loaded from wildfly-config.xml automatically in deployment

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8245?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-8245. ------------------------------------ Resolution: Rejected > AuthenticationContext should not be loaded from wildfly-config.xml automatically in deployment > ---------------------------------------------------------------------------------------------- > > Key: WFLY-8245 > URL: https://issues.jboss.org/browse/WFLY-8245 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > In case when wildfly-config.xml is located in deployment and application server does not have configured default-authentication-context for Elytron subsystem, then AuthenticationContext is automatically parsed from wildfly-config.xml. > In case when default-authentication-context for Elytron subsystem is configured, then AuthenticationContext is correctly loaded from application server. > If this is intended then it should be reflect in documentation - it currently says that "... they can make use of a configuration file using the _parseAuthenticationClientConfiguration(URI)_ method ...", but in current implementation it is parsed automatically. > [~dlofthouse] Could you please clarify whether this is intended change or it is an issue? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8296) CredentialStore, set own security provider through java security config file leads to NoClassDefFoundError for custom implementation class

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8296?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-8296: -------------------------------------- Assignee: (was: Darran Lofthouse) > CredentialStore, set own security provider through java security config file leads to NoClassDefFoundError for custom implementation class > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-8296 > URL: https://issues.jboss.org/browse/WFLY-8296 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > > When I want to define own Custom Elytron Provider through modification of Java security provider configuration I got exception about NoClassDefFoundError on CustomImplementation class. But this class is located in same jar file as Custom Elytron Provider. > I need it to define provider-name in credential-store. Is there some additional step which I missed? > Jar file is attached and it is same one as here https://issues.jboss.org/browse/JBEAP-8238 from [~pskopek] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3047) CredentialStore, set own security provider through java security config file leads to NoClassDefFoundError for custom implementation class

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3047?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-8296 to WFCORE-3047: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-3047 (was: WFLY-8296) Component/s: Security (was: Security) > CredentialStore, set own security provider through java security config file leads to NoClassDefFoundError for custom implementation class > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3047 > URL: https://issues.jboss.org/browse/WFCORE-3047 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > > When I want to define own Custom Elytron Provider through modification of Java security provider configuration I got exception about NoClassDefFoundError on CustomImplementation class. But this class is located in same jar file as Custom Elytron Provider. > I need it to define provider-name in credential-store. Is there some additional step which I missed? > Jar file is attached and it is same one as here https://issues.jboss.org/browse/JBEAP-8238 from [~pskopek] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3047) CredentialStore, set own security provider through java security config file leads to NoClassDefFoundError for custom implementation class

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3047?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-3047. -------------------------------------- Resolution: Rejected > CredentialStore, set own security provider through java security config file leads to NoClassDefFoundError for custom implementation class > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3047 > URL: https://issues.jboss.org/browse/WFCORE-3047 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > > When I want to define own Custom Elytron Provider through modification of Java security provider configuration I got exception about NoClassDefFoundError on CustomImplementation class. But this class is located in same jar file as Custom Elytron Provider. > I need it to define provider-name in credential-store. Is there some additional step which I missed? > Jar file is attached and it is same one as here https://issues.jboss.org/browse/JBEAP-8238 from [~pskopek] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8300) standalone-picketlink.xml boots with lots of errors

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8300?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-8300: -------------------------------------- Assignee: (was: Darran Lofthouse) > standalone-picketlink.xml boots with lots of errors > --------------------------------------------------- > > Key: WFLY-8300 > URL: https://issues.jboss.org/browse/WFLY-8300 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Tomaz Cerar > > If you try to run standalone-picketlink.xml server configuration, it's boot fails with lots of problems. They look related to elytron changes, but I am not sure. > {noformat} > 15:27:36,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "picketlink-identity-management"), > ("partition-manager" => "jpa.emf.modules.partition.manager") > ]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.picketlink-identity-management.\"jpa.emf.modules.partition.manager\".\"jpa.config\".jpa-store" => "org.jboss.msc.service.StartException in service jb > oss.picketlink-identity-management.\"jpa.emf.modules.partition.manager\".\"jpa.config\".jpa-store: Failed to start service > Caused by: org.picketlink.idm.config.SecurityConfigurationException: WFLYPL0050: Entities module not found [my.module]."}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.picketlink-identity-management.\"jpa.emf.modules.partition.manager\".\"jpa.config\".jpa-store"] > } > 15:27:36,477 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("host" => "default-host"), > ("setting" => "http-invoker") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory. > application-http-authentication]"] > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8301) Picketlink trust domain config needs to be in attribute and not path

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8301?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-8301: -------------------------------------- Assignee: (was: Darran Lofthouse) > Picketlink trust domain config needs to be in attribute and not path > -------------------------------------------------------------------- > > Key: WFLY-8301 > URL: https://issues.jboss.org/browse/WFLY-8301 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Tomaz Cerar > > Currently trustdomain for PL federation is configured by adding new sub resource under idenity-provider > Problem is that name of the trust domain resource you add is an url. > In case that URL is ipv6 one in square brackets [::1] this makes it a invalid path. > Currently testsuite relies on this to work, and by some miracle it works when configured via XML, but trying to do so with CLI fails as [] are forbidden chars in path (resource name) > example of CLI command > {{/subsystem=picketlink-federation/federation=federation-simple-redirect-binding/identity-provider=idp-redirect.war/trust-domain=${public.ip}:add > /subsystem=picketlink-federation/federation=federation-redirect-with-signatures/identity-provider=idp-redirect-sig.war/trust-domain=${public.ip}:add > /subsystem=picketlink-federation/federation=federation-simple-post-binding/identity-provider=idp-post.war/trust-domain=${public.ip}:add > /subsystem=picketlink-federation/federation=federation-post-with-signatures/identity-provider=idp-post-sig.war/trust-domain=${public.ip}:add > /subsystem=picketlink-federation/federation=federation-with-metadata/identity-provider=idp-metadata.war/trust-domain=${public.ip}:add}} > where ${public.ip} can be 127.0.01 or [::1] > I think given that TrustDomainResourceDefinition has no attributes beyond own name. > it could be converted to a List<String> on parent resource. > or name should be used only for id, with additional attribute that would represent domain. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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