May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4496) Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4496?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-11781 to WFCORE-4496: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4496 (was: WFLY-11781) Component/s: Security (was: Security) Affects Version/s: (was: 15.0.1.Final) > Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm > ------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-4496 > URL: https://issues.jboss.org/browse/WFCORE-4496 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Indrajit Ingawale > Assignee: Darran Lofthouse > Priority: Major > > It is requirement to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm . > -------------------------------------- > <security-domain name="TestDomain" default-realm="TestAggRealm" permission-mapper="default-permission-mapper" pre-realm-principal-transformer="test-transformer" security-event-listener="local-audit"> > <realm name="TestAggRealm" role-decoder="from-roles-attribute"/> > </security-domain> > . > . > <aggregate-realm name="TestAggRealm" authentication-realm="TestLdapRealm" authorization-realm="Test_Auth_LdapRealm"/> > -------------------------------------- > I think to achieve this there need to be something like "mid-realm-principal-transformer" in <aggregate-realm> only . -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11781) Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11781?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFLY-11781: --------------------------------------- Assignee: Darran Lofthouse > Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-11781 > URL: https://issues.jboss.org/browse/WFLY-11781 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Indrajit Ingawale > Assignee: Darran Lofthouse > Priority: Major > > It is requirement to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm . > -------------------------------------- > <security-domain name="TestDomain" default-realm="TestAggRealm" permission-mapper="default-permission-mapper" pre-realm-principal-transformer="test-transformer" security-event-listener="local-audit"> > <realm name="TestAggRealm" role-decoder="from-roles-attribute"/> > </security-domain> > . > . > <aggregate-realm name="TestAggRealm" authentication-realm="TestLdapRealm" authorization-realm="Test_Auth_LdapRealm"/> > -------------------------------------- > I think to achieve this there need to be something like "mid-realm-principal-transformer" in <aggregate-realm> only . -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1421) Elytron 1.2 user impacting issues

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1421?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1421. ----------------------------------- Resolution: Out of Date Latest release is now Elytron 1.9 > Elytron 1.2 user impacting issues > --------------------------------- > > Key: ELY-1421 > URL: https://issues.jboss.org/browse/ELY-1421 > Project: WildFly Elytron > Issue Type: Tracker > Reporter: Martin Choma > Assignee: Martin Choma > Priority: Trivial > > This issue is for tracking changes in Elytron 1.2 which brings new configuration options to users. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-369) SecurityIdentity-based self-service

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-369?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-369. ---------------------------------- Assignee: Diana Vilkolakova Resolution: Out of Date Marking as out of date, [~dvilkola] has already created a demo showing how self service can be possible. > SecurityIdentity-based self-service > ----------------------------------- > > Key: ELY-369 > URL: https://issues.jboss.org/browse/ELY-369 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI > Reporter: David Lloyd > Assignee: Diana Vilkolakova > Priority: Major > > We may need to provide the ability to allow users to manage their accounts in various ways. > * Password reset -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1497) Support Modular Crypt Format (MCF) password in Bcrypt mapper

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1497?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1497. ----------------------------------- Fix Version/s: 1.9.0.Final Assignee: Darran Lofthouse Resolution: Out of Date Modular crypt support is added to the JDBC SecurityRealm from WildFly 17 and Elytron 1.9.0.Final. > Support Modular Crypt Format (MCF) password in Bcrypt mapper > ------------------------------------------------------------ > > Key: ELY-1497 > URL: https://issues.jboss.org/browse/ELY-1497 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Passwords > Affects Versions: 1.1.7.Final > Reporter: Tom Stiemerling > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.Final > > > Currently BCrypt mapper for DB realm does not support MCF format passwords (which does not require explicit salt or iterations): > {noformat} > 17:42:28,328 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 3) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("jdbc-realm" => "DatabaseRealm") > ]) - failure description: "WFLYCTL0155: 'salt-index' may not be null" > {noformat} > Support should be added to support MCF password so only single column needed in DB. > Logic: > {code} > if (password && !salt && !iterations) > assume MCF format password > else if (password && salt && iterations) > assume BCrypt (b64) password, etc > else > error > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1560) Modularize Elytron to improve layered product support

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1560?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1560. ----------------------------------- Fix Version/s: 1.9.0.Final Assignee: Darran Lofthouse Resolution: Out of Date > Modularize Elytron to improve layered product support > ----------------------------------------------------- > > Key: ELY-1560 > URL: https://issues.jboss.org/browse/ELY-1560 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Ilia Vassilev > Assignee: Darran Lofthouse > Priority: Major > Labels: improvement > Fix For: 1.9.0.Final > > > Some layered products/projects might need access to specific utilitarian classes from Elytron, for example, BRMS' use of https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/.... > I suggest we split Elytron's utility classes into a new module which can then be easily integrated into other products/projects. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12134) Add org.infinispan:infinispan-multimap, org.infinispan:infinispan-clustered-counter, org.infinispan:infinispan-clustered-lock modules

by Sergey Aganin (Jira)

[ https://issues.jboss.org/browse/WFLY-12134?page=com.atlassian.jira.plugin... ] Sergey Aganin commented on WFLY-12134: -------------------------------------- This is a good proposal. Will it implement in the near future? [~pferraro], Thanks. > Add org.infinispan:infinispan-multimap, org.infinispan:infinispan-clustered-counter, org.infinispan:infinispan-clustered-lock modules > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12134 > URL: https://issues.jboss.org/browse/WFLY-12134 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 17.0.0.Beta1 > Reporter: Sergey Aganin > Assignee: Paul Ferraro > Priority: Major > > Please add the modules such that users can use the new features of Infinispan. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1620) Support of ASN1 enumerated into ASN1Decoder

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1620?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1620: --------------------------------------- [~mmazanek] This change was originally included in the OCSP changes, is that still the case? > Support of ASN1 enumerated into ASN1Decoder > ------------------------------------------- > > Key: ELY-1620 > URL: https://issues.jboss.org/browse/ELY-1620 > Project: WildFly Elytron > Issue Type: Task > Components: X.500 > Reporter: Jan Kalina > Priority: Critical > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1806) Release WildFly Elytron 1.9.0.Final

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1806?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1806. ----------------------------------- Fix Version/s: 1.9.0.Final (was: 1.10.0.CR1) Resolution: Done > Release WildFly Elytron 1.9.0.Final > ----------------------------------- > > Key: ELY-1806 > URL: https://issues.jboss.org/browse/ELY-1806 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12135) Error deploying web service without http-listener (only https-listener)

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12135?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12135: ---------------------------------- Summary: Error deploying web service without http-listener (only https-listener) (was: error deploying web service without http-listener (only https-listener) ) > Error deploying web service without http-listener (only https-listener) > ------------------------------------------------------------------------ > > Key: WFLY-12135 > URL: https://issues.jboss.org/browse/WFLY-12135 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 17.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Jim Ma > Priority: Major > > Deploying a application with only a https-listener (default http-listener was removed) gives error: > Caused by: java.lang.IllegalStateException: WFLYUT0063: Could not find the port number listening for protocol HTTP/1.1 > at org.wildfly.extension.undertow.WebServerService.getPort(WebServerService.java:68) > at org.jboss.as.webservices.config.WebServerInfoImpl.getPort(WebServerInfoImpl.java:36) > at org.jboss.ws.common.management.AbstractServerConfig.getConnectorPort(AbstractServerConfig.java:328) > at org.jboss.ws.common.management.AbstractServerConfig.getWebServicePort(AbstractServerConfig.java:237) > at org.jboss.wsf.spi.metadata.config.SOAPAddressRewriteMetadata.getWebServicePort(SOAPAddressRewriteMetadata.java:66) > at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect$PortValue.getPortValue(EndpointAddressDeploymentAspect.java:224) > at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect$PortValue.getValue(EndpointAddressDeploymentAspect.java:217) > at org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect.start(EndpointAddressDeploymentAspect.java:84) > at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) > ... 5 more > A workaround is to use webservices configuration to define modify-wsdl-address and wsdl-port (for wsdl soap address rewriting) or jboss-webservices.xml to define wsdl.soapAddress.rewrite.wsdl-port. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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