June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-819) LdapExt login module fetches to many attributes in RoleSearch

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-819?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-819: -------------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1086795|https://bugzilla.redhat.com/show_bug.cgi?id=1086795] from POST to MODIFIED > LdapExt login module fetches to many attributes in RoleSearch > ------------------------------------------------------------- > > Key: SECURITY-819 > URL: https://issues.jboss.org/browse/SECURITY-819 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: PicketBox_4_0_21.Beta3 > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > An LDAP server with (lets say) 1000 users in a group. > When authentication, a query is done to retrieve the groups for the user. > Most LDAP servers will limit the attributes send back based on authorization of the user, but can be configured to return *all* information. > The cause is: > / Query for roles matching the role filter > SearchControls constraints = new SearchControls(); > constraints.setSearchScope(searchScope); > constraints.setTimeLimit(searchTimeLimit); > rolesSearch(ctx, constraints, username, userDN, recursion, 0); > this used to also have: > constraints.setReturningAttributes(new String[0]); > at some time this was taken out. > It needs to go back in -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1848) SASL GSSAPI requires client_password to be set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1848?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JGRP-1848: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1107614 > SASL GSSAPI requires client_password to be set > ---------------------------------------------- > > Key: JGRP-1848 > URL: https://issues.jboss.org/browse/JGRP-1848 > Project: JGroups > Issue Type: Bug > Reporter: Vojtech Juranek > Assignee: Tristan Tarrant > > SASL GSSAPI requires client_password to be set otherwise faisl with NPE: > {noformat} > Caused by: java.lang.NullPointerException > at org.jgroups.protocols.SASL.init(SASL.java:179) > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861) > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481) > at org.jgroups.JChannel.init(JChannel.java:849) > at org.jgroups.JChannel.<init>(JChannel.java:159) > at org.jgroups.JChannel.<init>(JChannel.java:129) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:373) > ... 124 more > {noformat} > GSSAPI shouldn't require neither login nor passowrd and should use those provided in referred login module (if it's set). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1849) Misconfigured SASL protocol can fail with NPE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1849?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JGRP-1849: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1107615 > Misconfigured SASL protocol can fail with NPE > --------------------------------------------- > > Key: JGRP-1849 > URL: https://issues.jboss.org/browse/JGRP-1849 > Project: JGroups > Issue Type: Bug > Reporter: Vojtech Juranek > Assignee: Tristan Tarrant > Priority: Optional > > Misconfigured JGroups SASL protocol (e.g. mech is not specified) can result into NPE: > {noformat} > Caused by: java.lang.NullPointerException > at org.jgroups.auth.sasl.SaslUtils.getSaslServerFactory(SaslUtils.java:118) [jgroups.jar:3.5.0.Beta7] > at org.jgroups.protocols.SASL.init(SASL.java:178) [jgroups.jar:3.5.0.Beta7] > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861) [jgroups.jar:3.5.0.Beta7] > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481) [jgroups.jar:3.5.0.Beta7] > at org.jgroups.JChannel.init(JChannel.java:849) [jgroups.jar:3.5.0.Beta7] > at org.jgroups.JChannel.<init>(JChannel.java:159) [jgroups.jar:3.5.0.Beta7] > at org.jgroups.JChannel.<init>(JChannel.java:129) [jgroups.jar:3.5.0.Beta7] > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:373) [infinispan-core.jar:7.0.0-SNAPSHOT] > ... 124 more > {noformat} > It should fail more gracefully, e.g. throw some custom exception with details what's wrong with configuration. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1847) SASL GSSAPI auth doesn't use configured login_module

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1847?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JGRP-1847: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1107613 > SASL GSSAPI auth doesn't use configured login_module > ---------------------------------------------------- > > Key: JGRP-1847 > URL: https://issues.jboss.org/browse/JGRP-1847 > Project: JGroups > Issue Type: Bug > Reporter: Vojtech Juranek > Assignee: Tristan Tarrant > > When referring GSSAPI login module (e.g. kerberos login module in WildFly) in jgroups sasl setup, the login module seems to be ignored. JGroups try to log-in with different principal than one configured in login module (it uses default principal {{jgroups/server_name}}) and also I don't see any attempt to use WildFly login module in kerberos log. > Not sure if related, but when I setup principal {{jgroups/server_name}} in Kerberos, authentication also fails and again it I don't observe any attempt to log-in in Kerberos log. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1849) Misconfigured SASL protocol can fail with NPE

by Vojtech Juranek (JIRA)

Vojtech Juranek created JGRP-1849: ------------------------------------- Summary: Misconfigured SASL protocol can fail with NPE Key: JGRP-1849 URL: https://issues.jboss.org/browse/JGRP-1849 Project: JGroups Issue Type: Bug Reporter: Vojtech Juranek Assignee: Tristan Tarrant Priority: Optional Misconfigured JGroups SASL protocol (e.g. mech is not specified) can result into NPE: {noformat} Caused by: java.lang.NullPointerException at org.jgroups.auth.sasl.SaslUtils.getSaslServerFactory(SaslUtils.java:118) [jgroups.jar:3.5.0.Beta7] at org.jgroups.protocols.SASL.init(SASL.java:178) [jgroups.jar:3.5.0.Beta7] at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861) [jgroups.jar:3.5.0.Beta7] at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481) [jgroups.jar:3.5.0.Beta7] at org.jgroups.JChannel.init(JChannel.java:849) [jgroups.jar:3.5.0.Beta7] at org.jgroups.JChannel.<init>(JChannel.java:159) [jgroups.jar:3.5.0.Beta7] at org.jgroups.JChannel.<init>(JChannel.java:129) [jgroups.jar:3.5.0.Beta7] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:373) [infinispan-core.jar:7.0.0-SNAPSHOT] ... 124 more {noformat} It should fail more gracefully, e.g. throw some custom exception with details what's wrong with configuration. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1848) SASL GSSAPI requires client_password to be set

by Vojtech Juranek (JIRA)

Vojtech Juranek created JGRP-1848: ------------------------------------- Summary: SASL GSSAPI requires client_password to be set Key: JGRP-1848 URL: https://issues.jboss.org/browse/JGRP-1848 Project: JGroups Issue Type: Bug Reporter: Vojtech Juranek Assignee: Tristan Tarrant SASL GSSAPI requires client_password to be set otherwise faisl with NPE: {noformat} Caused by: java.lang.NullPointerException at org.jgroups.protocols.SASL.init(SASL.java:179) at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861) at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481) at org.jgroups.JChannel.init(JChannel.java:849) at org.jgroups.JChannel.<init>(JChannel.java:159) at org.jgroups.JChannel.<init>(JChannel.java:129) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:373) ... 124 more {noformat} GSSAPI shouldn't require neither login nor passowrd and should use those provided in referred login module (if it's set). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1847) SASL GSSAPI auth doesn't use configured login_module

by Vojtech Juranek (JIRA)

Vojtech Juranek created JGRP-1847: ------------------------------------- Summary: SASL GSSAPI auth doesn't use configured login_module Key: JGRP-1847 URL: https://issues.jboss.org/browse/JGRP-1847 Project: JGroups Issue Type: Bug Reporter: Vojtech Juranek Assignee: Tristan Tarrant When referring GSSAPI login module (e.g. kerberos login module in WildFly) in jgroups sasl setup, the login module seems to be ignored. JGroups try to log-in with different principal than one configured in login module (it uses default principal {{jgroups/server_name}}) and also I don't see any attempt to use WildFly login module in kerberos log. Not sure if related, but when I setup principal {{jgroups/server_name}} in Kerberos, authentication also fails and again it I don't observe any attempt to log-in in Kerberos log. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-522) kie-maven-plugin "file encoding" should be configurable.

by Takami Hirata (JIRA)

Takami Hirata created DROOLS-522: ------------------------------------ Summary: kie-maven-plugin "file encoding" should be configurable. Key: DROOLS-522 URL: https://issues.jboss.org/browse/DROOLS-522 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 6.1.0.Beta4 Reporter: Takami Hirata Assignee: Mark Proctor When generating kjar using kie-maven-plugin, file encoding of DRLs and other plain text file should be configurable. Default value of encoding should refer {code}${project.build.sourceEncoding}{code}. Maven Guideline: http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+En... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3014) jboss-web schema not hosted at http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3014?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-3014: ----------------------------------- PR addresses different problem all together, Scope of this issue should be just to upload current schemas on jboss.org. > jboss-web schema not hosted at http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd > --------------------------------------------------------------------------------- > > Key: WFLY-3014 > URL: https://issues.jboss.org/browse/WFLY-3014 > Project: WildFly > Issue Type: Documentation > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Environment: Not applicable > Reporter: Ray DeCampo > Assignee: Tomaz Cerar > Priority: Minor > Labels: xml, xml_schema > > The docs/schema/jboss-web_8_0.xsd file included with WildFly 8.0.0.Final indicates that the schema location is http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd. However, that URI does not return the schema file but a 404 instead (see http://www.jboss.org/j2ee/schema/ for a listing of the files there). > The file should be hosted where the schema document indicates or the schema should be updated to reflect the proper URI of the schema. Without it third party tools cannot assist in ensuring that the XML is well-formed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3014) jboss-web schema not hosted at http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3014?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-3014: --------------------------------- Assignee: Emmanuel Hugonnet (was: Tomaz Cerar) > jboss-web schema not hosted at http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd > --------------------------------------------------------------------------------- > > Key: WFLY-3014 > URL: https://issues.jboss.org/browse/WFLY-3014 > Project: WildFly > Issue Type: Documentation > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Environment: Not applicable > Reporter: Ray DeCampo > Assignee: Emmanuel Hugonnet > Priority: Minor > Labels: xml, xml_schema > > The docs/schema/jboss-web_8_0.xsd file included with WildFly 8.0.0.Final indicates that the schema location is http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd. However, that URI does not return the schema file but a 404 instead (see http://www.jboss.org/j2ee/schema/ for a listing of the files there). > The file should be hosted where the schema document indicates or the schema should be updated to reflect the proper URI of the schema. Without it third party tools cannot assist in ensuring that the XML is well-formed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

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