September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1331) Use connection-url to get database connection when connection properties for datasource-class is empty

by Lin Gao (JIRA)

Lin Gao created JBJCA-1331: ------------------------------ Summary: Use connection-url to get database connection when connection properties for datasource-class is empty Key: JBJCA-1331 URL: https://issues.jboss.org/browse/JBJCA-1331 Project: IronJacamar Issue Type: Task Components: JDBC Affects Versions: WildFly/IronJacamar 1.3.4.Final Reporter: Lin Gao Assignee: Lin Gao Fixes of JBJCA-1312 will fail the old configuration where the connection-url is used. In the compatibility point of view, we should try to use {{connection-url}} & {{driver-class}} to get the database connection if the connection properties are empty && datasource-class != null. A warning message should be printed to encourage users to use DataSource for database connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1316) patch apply command not working as expected in non-interactive mode in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1316?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1316: ------------------------------------------------- Vlado Pakan <vpakan(a)redhat.com> changed the Status of [bug 1290290|https://bugzilla.redhat.com/show_bug.cgi?id=1290290] from POST to MODIFIED > patch apply command not working as expected in non-interactive mode in domain mode > ----------------------------------------------------------------------------------- > > Key: WFCORE-1316 > URL: https://issues.jboss.org/browse/WFCORE-1316 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 2.0.8.Final > > > CLI patch apply command is misleading when the --host option is used. In non-interactive mode applies the patch to the local installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7198) Add support for Elytron SecurityDomain in IIOP-enabled EJBs

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/WFLY-7198?page=com.atlassian.jira.plugin.... ] Stefan Guilhen updated WFLY-7198: --------------------------------- Description: With https://issues.jboss.org/browse/WFLY-5689 we now have a way to map security domains as defined within deployment descriptors to Elytron security domains in the EJB3 subsystem. This means that IIOP-enabled beans should make use of the Elytron security framework to authenticate and authorize incoming requests if such a mapping exists for the EJB application. (was: With https://issues.jboss.org/browse/WFLY-5689 we now have a way to map security domains as defined within deployment descriptors to Elytron security domains in the EJB3 subsystem. This means that IIOP-enabled beans should make use of the Elytron security framework to authenticate and authorize incoming requests.) > Add support for Elytron SecurityDomain in IIOP-enabled EJBs > ----------------------------------------------------------- > > Key: WFLY-7198 > URL: https://issues.jboss.org/browse/WFLY-7198 > Project: WildFly > Issue Type: Feature Request > Components: EJB, IIOP > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > Labels: affects_elytron > > With https://issues.jboss.org/browse/WFLY-5689 we now have a way to map security domains as defined within deployment descriptors to Elytron security domains in the EJB3 subsystem. This means that IIOP-enabled beans should make use of the Elytron security framework to authenticate and authorize incoming requests if such a mapping exists for the EJB application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7198) Add support for Elytron SecurityDomain in IIOP-enabled EJBs

by Stefan Guilhen (JIRA)

Stefan Guilhen created WFLY-7198: ------------------------------------ Summary: Add support for Elytron SecurityDomain in IIOP-enabled EJBs Key: WFLY-7198 URL: https://issues.jboss.org/browse/WFLY-7198 Project: WildFly Issue Type: Feature Request Components: EJB, IIOP Reporter: Stefan Guilhen Assignee: Stefan Guilhen With https://issues.jboss.org/browse/WFLY-5689 we now have a way to map security domains as defined within deployment descriptors to Elytron security domains in the EJB3 subsystem. This means that IIOP-enabled beans should make use of the Elytron security framework to authenticate and authorize incoming requests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7197) Allow configuration of an Elytron SSLContext in the IIOP subsystem

by Stefan Guilhen (JIRA)

Stefan Guilhen created WFLY-7197: ------------------------------------ Summary: Allow configuration of an Elytron SSLContext in the IIOP subsystem Key: WFLY-7197 URL: https://issues.jboss.org/browse/WFLY-7197 Project: WildFly Issue Type: Feature Request Components: IIOP Reporter: Stefan Guilhen Assignee: Tomasz Adamski Currently the IIOP subsystem defines an attribute that references a JSSE security domain to obtain the key and trust managers used by the SSLSocketFactory to build an SSLContext instance. With Elytron we now have a new capability that exposes SSLContext instances and we should be able to use that in the IIOP subsystem. A new attribute must be added to allow for the specification of the Elytron SSLContext that should be used. The SSLSocketFactory will still support the old JSSE-based configuration but will be able to make use of Elytron's centralized SSL configuration to obtain an SSLContext. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7197) Allow configuration of an Elytron SSLContext in the IIOP subsystem

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/WFLY-7197?page=com.atlassian.jira.plugin.... ] Stefan Guilhen reassigned WFLY-7197: ------------------------------------ Assignee: Stefan Guilhen (was: Tomasz Adamski) > Allow configuration of an Elytron SSLContext in the IIOP subsystem > ------------------------------------------------------------------ > > Key: WFLY-7197 > URL: https://issues.jboss.org/browse/WFLY-7197 > Project: WildFly > Issue Type: Feature Request > Components: IIOP > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > Labels: affects_elytron > > Currently the IIOP subsystem defines an attribute that references a JSSE security domain to obtain the key and trust managers used by the SSLSocketFactory to build an SSLContext instance. > With Elytron we now have a new capability that exposes SSLContext instances and we should be able to use that in the IIOP subsystem. A new attribute must be added to allow for the specification of the Elytron SSLContext that should be used. The SSLSocketFactory will still support the old JSSE-based configuration but will be able to make use of Elytron's centralized SSL configuration to obtain an SSLContext. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBAS-7853) Migrate sessions that use jvmRoute to nodes where they are local cached

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBAS-7853?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBAS-7853: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1233400|https://bugzilla.redhat.com/show_bug.cgi?id=1233400] from MODIFIED to ON_QA > Migrate sessions that use jvmRoute to nodes where they are local cached > ----------------------------------------------------------------------- > > Key: JBAS-7853 > URL: https://issues.jboss.org/browse/JBAS-7853 > Project: Application Server 3 4 5 and 6 > Issue Type: Task > Components: Clustering, Web (Tomcat) service > Reporter: Brian Stansberry > Assignee: Paul Ferraro > Fix For: 6.0.0.CR1 > > > Detect situation where a session is not stored locally in infinispan on the node that is servicing it. (This could happen with DIST following a rehash). If detected, determine the jvmRoute of a node where the session is local. Change the jvmRoute of session cookie to that node, which will trigger the next request going there. > Note that this requires that the request that is changing the jvmRoute also replicates the session synchronously. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-286) HTTP Digest Authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-286?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-286: -------------------------------------- Design notes for nonce handling: - https://developer.jboss.org/docs/DOC-55755 > HTTP Digest Authentication > -------------------------- > > Key: ELY-286 > URL: https://issues.jboss.org/browse/ELY-286 > Project: WildFly Elytron > Issue Type: Sub-task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta11 > > > Original Digest RFC [https://tools.ietf.org/html/rfc2069] > Current Digest RFC [https://tools.ietf.org/html/rfc2617] > HTTP 1.1 Authentication (Updates RFC2617) [https://tools.ietf.org/html/rfc7235] > Draft currently under discussion - [https://datatracker.ietf.org/doc/draft-ietf-httpauth-digest/] > RFC7616 Now Proposed Standard > "HTTP Digest Access Authentication", September 2015 > [https://www.rfc-editor.org/info/rfc7616] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-639) SecurityIdentity and PeerIdentity should have more runAs* variants

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-639?page=com.atlassian.jira.plugin.sy... ] David Lloyd updated ELY-639: ---------------------------- Description: The XxxIdentity classes have fewer runAs modes than (for example) Contextual objects do. Unifying these types would be ideal, but I'd settle for adding the missing types, including the {{Exception*}} functional types from WildFly Common. (was: The *Identity classes have fewer runAs modes than (for example) Contextual objects do. Unifying these types would be ideal, but I'd settle for adding the missing types, including the {{Exception*}} functional types from WildFly Common.) > SecurityIdentity and PeerIdentity should have more runAs* variants > ------------------------------------------------------------------ > > Key: ELY-639 > URL: https://issues.jboss.org/browse/ELY-639 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Fix For: 1.1.0.Beta10 > > > The XxxIdentity classes have fewer runAs modes than (for example) Contextual objects do. Unifying these types would be ideal, but I'd settle for adding the missing types, including the {{Exception*}} functional types from WildFly Common. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-639) SecurityIdentity and PeerIdentity should have more runAs* variants

by David Lloyd (JIRA)

David Lloyd created ELY-639: ------------------------------- Summary: SecurityIdentity and PeerIdentity should have more runAs* variants Key: ELY-639 URL: https://issues.jboss.org/browse/ELY-639 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Reporter: David Lloyd Fix For: 1.1.0.Beta10 The *Identity classes have fewer runAs modes than (for example) Contextual objects do. Unifying these types would be ideal, but I'd settle for adding the missing types, including the {{Exception*}} functional types from WildFly Common. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016