June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3072) Support Referrals for security realms using LDAP for authentication or group loading.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3072?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3072: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1066488|https://bugzilla.redhat.com/show_bug.cgi?id=1066488] from VERIFIED to CLOSED > Support Referrals for security realms using LDAP for authentication or group loading. > ------------------------------------------------------------------------------------- > > Key: WFLY-3072 > URL: https://issues.jboss.org/browse/WFLY-3072 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.1.0.CR2, 8.1.0.Final > > > I see the following scenarios to cover for this: - > - Authentication - A search is performed e.g against 'uid' and a referral is encountered, the URL needs to be extracted from the referral and a new connection created using the referral URL to load any additional attributes for the user, the referral URL is then used to establish the connection as the user to verify that their password is correct. > Group loading then has a couple of issues, firstly where the user was a referral. > The search for group membership information is a fresh start but now we potentially have 2 simple named and 2 distinguished names that could be referenced from the group object. We may want a config option to specify which one to actually use and even possibly use both. > Next could a group also be a referral, i.e. it contains the reference to the user as an attribute so was matched in the search but is also a referral to the true named group in another location. In this situation I suggest any iterative search takes into account the context containing the actual group definition and continues the search from there. > And then where the principal contains an attribute that references, this one should be a simple following of a referral and once followed continue the attribute loading using the new connection. > The connection manager logic is going to need reworking, ideally for a referral we should check if we have a connection definition that matches based on the URL returned otherwise we will need to try and establish a connection based on the settings of the last connection used, this probably also introduces a notion of some form of connection stack of the connections used for the current request - referrals could have us bouncing back and forth so connections should be cached and re-used where possible during authentication and group loading. > * Connection Settings * > We are going to need to support two different modes in relation to the 'java.naming.referral' property, follow and throw. > - *follow* - In this mode when the InitialDirContext encounters a referral during a search it will automatically follow it, this means automatically connecting to the server in the URL. This is fine if the remaining connection settings are valid for the alternative server e.g. same bindDN and credential. We however need to take the following into account for subsequent operations such as password validation or further queries. > - *throw* - When a referral is encountered and exception will be thrown instead, this mode should make it easier to have some more advanced referral handling logic that allows us control of which connection we subsequently use, e.g. we could not use a completely different host name to the one in the referral or use a different bind DN / credential pair. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2995: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1066606|https://bugzilla.redhat.com/show_bug.cgi?id=1066606] from VERIFIED to CLOSED > Using a log4j appender as a custom-handler should invoke the activateOptions if required > ---------------------------------------------------------------------------------------- > > Key: WFLY-2995 > URL: https://issues.jboss.org/browse/WFLY-2995 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.1.0.CR1, 8.1.0.Final > > > Currently the {{OptionHandler.activateOptions}} is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3133) Misleading error message for add-user username requirements.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3133?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3133: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1062611|https://bugzilla.redhat.com/show_bug.cgi?id=1062611] from VERIFIED to CLOSED > Misleading error message for add-user username requirements. > ------------------------------------------------------------ > > Key: WFLY-3133 > URL: https://issues.jboss.org/browse/WFLY-3133 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.1.0.CR1, 8.1.0.Final > > > The current error message is: - > {code} > JBAS015239: Only alpha/numeric usernames accepted. > {code} > However a small set of symbols are allowed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-314) EE subsystem global modules should support annotation flag

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-314?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-314: ---------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1009166|https://bugzilla.redhat.com/show_bug.cgi?id=1009166] from VERIFIED to CLOSED > EE subsystem global modules should support annotation flag > ---------------------------------------------------------- > > Key: WFLY-314 > URL: https://issues.jboss.org/browse/WFLY-314 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EE > Reporter: James Livingston > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Annotation indexes aren't imported with modules by default, but you can specify the annotation flag in the manifest Dependencies line or the annotation attribute in jboss-deployment-structure.xml. > The EE subsystem's global modules section does not let you specify that option, which means you can't define EJB interceptors and similar things in global modules. It should let you do that. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3287) Upgrade vfs to 3.2.5.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3287?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3287: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1091293|https://bugzilla.redhat.com/show_bug.cgi?id=1091293] from VERIFIED to CLOSED > Upgrade vfs to 3.2.5.Final > -------------------------- > > Key: WFLY-3287 > URL: https://issues.jboss.org/browse/WFLY-3287 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: VFS > Affects Versions: 8.1.0.CR1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.1.0.CR2, 8.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3241) KDC server does not bind to correct address

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3241?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3241: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1085709|https://bugzilla.redhat.com/show_bug.cgi?id=1085709] from VERIFIED to CLOSED > KDC server does not bind to correct address > ------------------------------------------- > > Key: WFLY-3241 > URL: https://issues.jboss.org/browse/WFLY-3241 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.1.0.CR1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3094) Warn if there is no resource bound for address-settings expiry and dead-letter addresses

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3094?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3094: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1014099|https://bugzilla.redhat.com/show_bug.cgi?id=1014099] from VERIFIED to CLOSED > Warn if there is no resource bound for address-settings expiry and dead-letter addresses > ---------------------------------------------------------------------------------------- > > Key: WFLY-3094 > URL: https://issues.jboss.org/browse/WFLY-3094 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.1.0.CR1, 8.1.0.Final > > > Warns the user if a address-setting has defined an expiry-address or a dead-letter-address with no queue bound for them as this will result in unintended message loss. > WildFly default full configuration specifies an expiry address (jms.queue.ExpiryQueue) and dead-letter-addres (jms.queue.DLQ) for the # address settings (i.e. matching all addresses). > To have a consistent configuration, we must also define 2 queues that will be bound to these settings. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2633) Cannot use deployments with same runtime-name in a domain

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2633?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2633: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1040621|https://bugzilla.redhat.com/show_bug.cgi?id=1040621] from VERIFIED to CLOSED > Cannot use deployments with same runtime-name in a domain > --------------------------------------------------------- > > Key: WFLY-2633 > URL: https://issues.jboss.org/browse/WFLY-2633 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > > The check for duplicate runtime-name in a server group on startup is too aggressive. It is incorrectly throwing an error on startup if there are any duplicate runtime-names in the whole domain, instead of just in a single server group. > Steps to Reproduce: > 1. Start a single HC/DC > 2. deploy --name=foo1 --runtime-name=bar --disabled testfile > 3. deploy --name=foo2 --runtime-name=bar --disabled testfile > 4. restart the DC/HC > Actual results: > JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > ... > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1348,9] > ... > Message: JBAS014664: An element of this type named 'bar' has already been declared > Expected results: > No errors -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-153) Fix logging of "Standard expiration of session X failed; switching to a brute force cleanup. Problem is null"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-153?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-153: ---------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 900552|https://bugzilla.redhat.com/show_bug.cgi?id=900552] from VERIFIED to CLOSED > Fix logging of "Standard expiration of session X failed; switching to a brute force cleanup. Problem is null" > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-153 > URL: https://issues.jboss.org/browse/WFLY-153 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 8.0.0.Alpha2 > > > I am seeing exception with missing reason > {noformat} > 19:54:12,862 WARN [org.apache.catalina.session.ManagerBase] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) JBAS018080: Standard expiration of session 7TYWbrkMf6UGi4WUu2Z3VUam failed; switching to a brute force cleanup. Problem is null > {noformat} > Looks like the actual exception is not well propagated to the message. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-352) Add sufficient TRACE / DEBUG logging to debug security realm configurations.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-352?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-352: ---------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 974324|https://bugzilla.redhat.com/show_bug.cgi?id=974324] from VERIFIED to CLOSED > Add sufficient TRACE / DEBUG logging to debug security realm configurations. > ---------------------------------------------------------------------------- > > Key: WFLY-352 > URL: https://issues.jboss.org/browse/WFLY-352 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Eric Rich > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.Beta1 > > Attachments: jboss-as-domain-management-7.1.2.Final-redhat-1.jar, log_mgmt_auth_calls.txt > > > When trying to diagnose LDAP or Admin Configuration issue in Domain mode there is currently no logging for any of the authentication information. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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