March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3145) Problem with HTTPS Failed to start the http-interface service

by Jasbir Sahota (JIRA)

Jasbir Sahota created WFLY-3145: ----------------------------------- Summary: Problem with HTTPS Failed to start the http-interface service Key: WFLY-3145 URL: https://issues.jboss.org/browse/WFLY-3145 Project: WildFly Issue Type: Support Request Security Level: Public (Everyone can see) Affects Versions: 8.0.0.Final Reporter: Jasbir Sahota Priority: Critical -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3105) Container-managed EXTENDED persistence context is always joined with transaction even if UNSYNCHRONIZED

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3105?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-3105: ------------------------------------ The https://github.com/wildfly/wildfly/pull/6065 change is to not join the extended persistence context to the transaction (via EntityManager.joinTransaction()) for UNSYNCHRONIZED. The added unit test failed before the change and passed after. > Container-managed EXTENDED persistence context is always joined with transaction even if UNSYNCHRONIZED > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-3105 > URL: https://issues.jboss.org/browse/WFLY-3105 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Affects Versions: 8.0.0.Final > Reporter: Christian Bauer > Assignee: Scott Marlow > Fix For: 8.0.1.Final > > > https://github.com/weld/wildfly/blob/master/testsuite/integration/basic/s... > Change this test to {code}@PersistenceContext(type = EXTENDED, synchronization = UNSYNCHRONIZED){code} and it will break. > Looks like an extended PC is always joined to the transaction and flushed on commit, the unsynchronized mode is ignored. From what I can see this is not specified and indeed would make the whole new UNSYNCHRONIZED feature kind of pointless. It's primary use case is propagation of unflushed/unsynchronized extended PC from a SFSB to other beans while keeping transactions intact. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2957) Refactor the SSL services within the security realms so that key and trust managers are injected instead of stores.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2957?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reopened WFLY-2957: ------------------------------------ > Refactor the SSL services within the security realms so that key and trust managers are injected instead of stores. > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2957 > URL: https://issues.jboss.org/browse/WFLY-2957 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > To cope with things like being able to reload trust stores after files have been modified some implementation details regarding file handling have leaked slightly into the SSLIdentityService which represents the servers identity - instead the key and trust manager instances should be injected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2957) Refactor the SSL services within the security realms so that key and trust managers are injected instead of stores.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2957?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2957: ----------------------------------- Priority: Critical (was: Major) > Refactor the SSL services within the security realms so that key and trust managers are injected instead of stores. > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2957 > URL: https://issues.jboss.org/browse/WFLY-2957 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 9.0.0.CR1 > > > To cope with things like being able to reload trust stores after files have been modified some implementation details regarding file handling have leaked slightly into the SSLIdentityService which represents the servers identity - instead the key and trust manager instances should be injected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2957) Refactor the SSL services within the security realms so that key and trust managers are injected instead of stores.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2957?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2957: ----------------------------------- Fix Version/s: 8.0.1.Final (was: 9.0.0.CR1) > Refactor the SSL services within the security realms so that key and trust managers are injected instead of stores. > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2957 > URL: https://issues.jboss.org/browse/WFLY-2957 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.1.Final > > > To cope with things like being able to reload trust stores after files have been modified some implementation details regarding file handling have leaked slightly into the SSLIdentityService which represents the servers identity - instead the key and trust manager instances should be injected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1750) RELAY2 : Address formats are not relayed.

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1750?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1750: -------------------------------- [~ammous] Not sure I understand the need for an AddressGenerator to be set in a bridge. Meanwhile, I created an {{ExtendedAddress}} and {{SiteUUID}} and {{SiteMaster}} are both subclasses of it, so you can add any data to them. I modified UnicastTestRpc slightly and used a config containing RELAY2, and data added to a SiteUUID is actually seen at the receiving end in a different site. Do you have a small test case that shows your problem ? (This is on branch JGRP-1750) > RELAY2 : Address formats are not relayed. > ----------------------------------------- > > Key: JGRP-1750 > URL: https://issues.jboss.org/browse/JGRP-1750 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.4.1 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5 > > > When defining a relay channel, we haven't the ability to set an AddressGenrator. Indeed, the Relayer uses its own AddressGenerator providing addresses of type SiteUUID. > This is particularly embarrassing in the following case: when we define a customized address format (like CanBeSiteMasterTopology or TopologyUUID) for members of two Sites A and B, address format is lost by crossing relay. Address type of messages sent by A to B are seen as SiteUUID at B side. > Suggestions: > - Making address format "relayable" ? > - Using the same (or an extended format) AddressGenerator of site Channel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2951) Enable alternative provider to be specified for loading key and trust stores.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2951?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reopened WFLY-2951: ------------------------------------ > Enable alternative provider to be specified for loading key and trust stores. > ----------------------------------------------------------------------------- > > Key: WFLY-2951 > URL: https://issues.jboss.org/browse/WFLY-2951 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > This is to allow pre-defined PKCS#11 providers to be referenced. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2951) Enable alternative provider to be specified for loading key and trust stores.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2951?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2951: ----------------------------------- Fix Version/s: 8.0.1.Final (was: 9.0.0.CR1) > Enable alternative provider to be specified for loading key and trust stores. > ----------------------------------------------------------------------------- > > Key: WFLY-2951 > URL: https://issues.jboss.org/browse/WFLY-2951 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > This is to allow pre-defined PKCS#11 providers to be referenced. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2890) Add support for PKCS#11 configuration within security realms.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2890?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2890: ----------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.1.Final) > Add support for PKCS#11 configuration within security realms. > ------------------------------------------------------------- > > Key: WFLY-2890 > URL: https://issues.jboss.org/browse/WFLY-2890 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: eap, management_security, > Fix For: 9.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-795) AdvancedLdap login module does not handle a user that has a slash character in the uid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-795?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-795: -------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1065476|https://bugzilla.redhat.com/show_bug.cgi?id=1065476] from MODIFIED to ON_QA > AdvancedLdap login module does not handle a user that has a slash character in the uid > -------------------------------------------------------------------------------------- > > Key: SECURITY-795 > URL: https://issues.jboss.org/browse/SECURITY-795 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Derek Horton > Fix For: Negotiation_2_2_7 > > Attachments: SECURITY-795.patch > > > AdvancedLdap login module does not handle a user that has a slash character in the uid. > For example, JBoss will fail to authenticate the following user correctly: > dn: uid=weird/user,ou=Users,dc=my-domain,dc=com > uid: weird/user > cn: Weird User -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 March 2014