May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10433) allow JPA apps to disable WildFly JTA platform/2lc initiators for Hibernate ORM 5.3+

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10433?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-10433: -------------------------------- Summary: allow JPA apps to disable WildFly JTA platform/2lc initiators for Hibernate ORM 5.3+ (was: allow JPA apps to disable WildFly JTA platform/2lc integration for Hibernate ORM 5.3+) > allow JPA apps to disable WildFly JTA platform/2lc initiators for Hibernate ORM 5.3+ > ------------------------------------------------------------------------------------ > > Key: WFLY-10433 > URL: https://issues.jboss.org/browse/WFLY-10433 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 13.0.0.CR1 > > > Some applications (e.g. Spring) may not want to use the WF 2lc RegionFactoryInitiator + JtaPlatform classes. To accommodate that need, following persistence unit configuration properties will help: > * wildfly.jpa.jtaplatform will default to true but if set to false, the WildFly JtaPlatform initiator for ORM 5.3+ (WildFlyCustomJtaPlatformInitiator), will not control Jta use in the Hibernate persistence unit (or session factory). > * wildfly.jpa.regionfactory will default to true but if set to false,the WildFly 2lc cache initiator for ORM (WildFlyCustomRegionFactoryInitiator) will not control 2lc use in the Hibernate persistence unit (or session factory). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-657) Wrong error message in OAuth2Client

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-657?page=com.atlassian.jira.plugin.sy... ] Farah Juma reassigned ELY-657: ------------------------------ Assignee: Justin Cook > Wrong error message in OAuth2Client > ----------------------------------- > > Key: ELY-657 > URL: https://issues.jboss.org/browse/ELY-657 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Mechanisms > Reporter: David Lloyd > Assignee: Justin Cook > Priority: Minor > > In OAuth2Client, if the bearer token callback is unsupported, an {{mechCallbackHandlerDoesNotSupportUserName}} is generated. There should be an error that is more specific to the token callback. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10434) Cached connection manager debug forcing closed connections unexpectedly

by Stephen Fikes (JIRA)

Stephen Fikes created WFLY-10434: ------------------------------------ Summary: Cached connection manager debug forcing closed connections unexpectedly Key: WFLY-10434 URL: https://issues.jboss.org/browse/WFLY-10434 Project: WildFly Issue Type: Bug Reporter: Stephen Fikes Assignee: Flavia Rainone When cached connection manager (CCM) debug is enabled, during the stack unwind for EJB remote calls, CCM debug is reporting leaked connections and force-closing them. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1287) Update CLIENT_CERT mechanism to use Scope.SSL_SESSION instead of SSLSession

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1287?page=com.atlassian.jira.plugin.s... ] Farah Juma reassigned ELY-1287: ------------------------------- Assignee: Justin Cook > Update CLIENT_CERT mechanism to use Scope.SSL_SESSION instead of SSLSession > --------------------------------------------------------------------------- > > Key: ELY-1287 > URL: https://issues.jboss.org/browse/ELY-1287 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Justin Cook > > This would mean even if the actual SSLSession is unavailable the integration still has the opportunity to provide a scope that represents the session. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3880) Provide Elytron alternative to RoleMappingLoginModule

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3880: ---------------------------------------- Summary: Provide Elytron alternative to RoleMappingLoginModule Key: WFCORE-3880 URL: https://issues.jboss.org/browse/WFCORE-3880 Project: WildFly Core Issue Type: Feature Request Components: Security Affects Versions: 4.0.0.Final Reporter: Darran Lofthouse In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron. Another workaround is to use direct roles from realm (e.g. LDAP ) in target (e.g. web.xml). But seems users tend to map IDM Roles to applicaiton roles. [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3666) Provide Elytron alternative to RoleMappingLoginModule

by Martin Mazanek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3666?page=com.atlassian.jira.plugi... ] Martin Mazanek reassigned WFCORE-3666: -------------------------------------- Assignee: Martin Mazanek > Provide Elytron alternative to RoleMappingLoginModule > ----------------------------------------------------- > > Key: WFCORE-3666 > URL: https://issues.jboss.org/browse/WFCORE-3666 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 4.0.0.Final > Reporter: Martin Choma > Assignee: Martin Mazanek > > In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron. > Another workaround is to use direct roles from realm (e.g. LDAP ) in target (e.g. web.xml). But seems users tend to map IDM Roles to applicaiton roles. > [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3879) Add subsystem component to use a custom audit endpoint

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3879: ---------------------------------------- Summary: Add subsystem component to use a custom audit endpoint Key: WFCORE-3879 URL: https://issues.jboss.org/browse/WFCORE-3879 Project: WildFly Core Issue Type: Feature Request Components: Security Affects Versions: 5.0.0.Alpha7 Reporter: Darran Lofthouse Assignee: Jan Kalina Elytron has the ability to create custom audit endpoints to develop your own audit logs. Nevertheless there is no configuration under the {{subsystem=elytron}} to configure a custom audit class (something like {{subsystem=elytron/custom-audit-log=example:add(...}} is needed). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-250) Create Jenkinsfile for Istio-and-Kiali Jenkins Job

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-250: --------------------------------------------- Summary: Create Jenkinsfile for Istio-and-Kiali Jenkins Job Key: SWSQE-250 URL: https://issues.jboss.org/browse/SWSQE-250 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-248) Update kiali rest python client

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-248?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy commented on SWSQE-248: --------------------------------------- PR sent: https://github.com/Kiali-QE/kiali-client-python/pull/2 > Update kiali rest python client > ------------------------------- > > Key: SWSQE-248 > URL: https://issues.jboss.org/browse/SWSQE-248 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Update kiali python client[1], changes are available here [2] > [1] - https://github.com/Kiali-QE/kiali-client-python > [2] - https://github.com/kiali/kiali/blob/master/routing/routes.go -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10433) allow JPA apps to disable WildFly JTA platform/2lc integration for Hibernate ORM 5.3+

by Scott Marlow (JIRA)

Scott Marlow created WFLY-10433: ----------------------------------- Summary: allow JPA apps to disable WildFly JTA platform/2lc integration for Hibernate ORM 5.3+ Key: WFLY-10433 URL: https://issues.jboss.org/browse/WFLY-10433 Project: WildFly Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 13.0.0.CR1 Some applications (e.g. Spring) may not want to use the WF 2lc RegionFactoryInitiator + JtaPlatform classes. To accommodate that need, following persistence unit configuration properties will help: * wildfly.jpa.jtaplatform will default to true but if set to false, the WildFly JtaPlatform initiator for ORM 5.3+ (WildFlyCustomJtaPlatformInitiator), will not control Jta use in the Hibernate persistence unit (or session factory). * wildfly.jpa.regionfactory will default to true but if set to false,the WildFly 2lc cache initiator for ORM (WildFlyCustomRegionFactoryInitiator) will not control 2lc use in the Hibernate persistence unit (or session factory). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018