[JBoss JIRA] Created: (JBAS-3653) Ldap*LoginModule fail to retrieve multiple role names when roleAttributeIsDN=true
by Scott M Stark (JIRA)
Ldap*LoginModule fail to retrieve multiple role names when roleAttributeIsDN=true
---------------------------------------------------------------------------------
Key: JBAS-3653
URL: http://jira.jboss.com/jira/browse/JBAS-3653
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: JBossAS-4.0.4.GA
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossAS-4.0.5.GA
Attachments: example2.ldif
For a schema like example2.ldif and a configuration like:
testLdapExample22 {
org.jboss.security.auth.spi.LdapExtLoginModule
java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
java.naming.provider.url="ldap://lamia/"
java.naming.security.authentication=simple
bindDN="cn=Root,dc=jboss,dc=org"
bindCredential=secret1
baseCtxDN="ou=People,o=example2,dc=jboss,dc=org"
baseFilter="(uid={0})"
rolesCtxDN="ou=Roles,o=example2,dc=jboss,dc=org";
roleFilter="(uid={0})"
roleAttributeID="memberOf"
roleAttributeIsDN="true"
roleNameAttributeID="cn"
roleRecursion=0
};
Only one role is being pulled from the cn=EchoGroup,ou=Roles,o=example2,dc=jboss,dc=org context, rather the both EchoGroup and TheDuke as only one of the cn attribute values is retrieved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBMESSAGING-407) XARecovery integration of JBossMessaging with JBossTS
by Madhusudhan Konda (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=all ]
Madhusudhan Konda updated JBMESSAGING-407:
------------------------------------------
Attachment: xarecovery-patch.txt
artifacts.zip
Please find the patch file with this message. I have also attached the compressed src and tests folders, just in case.
Testing is something which I had a bit of problem - as to how to simulate the server crash etc. Please see the tests/build.xml where I descibed the testing process. I am sure you'll have issues :)
Thanks
Madhu
> XARecovery integration of JBossMessaging with JBossTS
> -----------------------------------------------------
>
> Key: JBMESSAGING-407
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-407
> Project: JBoss Messaging
> Issue Type: Patch
> Components: Tests and Performance
> Environment: JBoss 4.0.3SP1, JBossTs 4.2GA, JBOSS Messagig 1.0.1CR2
> Reporter: Madhusudhan Konda
> Assigned To: Ovidiu Feodorov
> Fix For: 1.2.0.Alpha1
>
> Attachments: artifacts.zip, jms-recovery-patch-all.txt, jms.zip, JMSProviderXAResourceRecovery.java, xa.zip, xarecovery-patch.txt, XATestStandaloneRecovery.java
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> To make JBossMessaging XAResource as recoverable using JBossTS RecoveryManager
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Created: (JBCACHE-762) Configuration object enhancements
by Manik Surtani (JIRA)
Configuration object enhancements
---------------------------------
Key: JBCACHE-762
URL: http://jira.jboss.com/jira/browse/JBCACHE-762
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Manik Surtani
Assigned To: Manik Surtani
Fix For: 2.0.0
1. Why isn't there a CacheFactory.createCache() (using the default configuration)
2. I think it would be useful to have a static method in Configuration which returns the default config, so we could do: Cache c=new DefaultCacheFactory().createCache(Configuration.getDefault())
3. Configuration should have a copy() or clone() method, so we can reuse a config, and make small modifications
4. Make Configuration serializable (ship them around ?)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBAS-3652) Add EULA to licenses folder of distribution
by Ryan Campbell (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3652?page=all ]
Ryan Campbell updated JBAS-3652:
--------------------------------
Priority: Critical (was: Major)
> Add EULA to licenses folder of distribution
> -------------------------------------------
>
> Key: JBAS-3652
> URL: http://jira.jboss.com/jira/browse/JBAS-3652
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ryan Campbell
> Assigned To: Rajesh Rajasekaran
> Priority: Critical
> Fix For: JBossAS-4.0.5.GA
>
> Attachments: JBossEULA.doc, JBossEULA.pdf, JBossEULA.txt
>
>
> We need to include the attached EULA text file in all "licenses" folders of
> our distributions. It is an umbrella EULA that does not change the
> fact that our source code is open source...it simply applies a little more
> rigor around use of trademarks and logos as well as Export conditions.
> We do not need to retrofit this into existing builds, just new builds on an
> ongoing basis. Ex. JBoss AS 4.0.5 should include it.
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBAS-3652) Add EULA to licenses folder of distribution
by Ryan Campbell (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3652?page=all ]
Ryan Campbell updated JBAS-3652:
--------------------------------
Assignee: Rajesh Rajasekaran (was: Ryan Campbell)
Fix Version/s: JBossAS-4.0.5.GA
> Add EULA to licenses folder of distribution
> -------------------------------------------
>
> Key: JBAS-3652
> URL: http://jira.jboss.com/jira/browse/JBAS-3652
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ryan Campbell
> Assigned To: Rajesh Rajasekaran
> Fix For: JBossAS-4.0.5.GA
>
> Attachments: JBossEULA.doc, JBossEULA.pdf, JBossEULA.txt
>
>
> We need to include the attached EULA text file in all "licenses" folders of
> our distributions. It is an umbrella EULA that does not change the
> fact that our source code is open source...it simply applies a little more
> rigor around use of trademarks and logos as well as Export conditions.
> We do not need to retrofit this into existing builds, just new builds on an
> ongoing basis. Ex. JBoss AS 4.0.5 should include it.
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Moved: (JBAS-3652) Add EULA to licenses folder of distribution
by Ryan Campbell (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3652?page=all ]
Ryan Campbell moved JBQA-465 to JBAS-3652:
------------------------------------------
Project: JBoss Application Server (was: JBoss QA)
Key: JBAS-3652 (was: JBQA-465)
> Add EULA to licenses folder of distribution
> -------------------------------------------
>
> Key: JBAS-3652
> URL: http://jira.jboss.com/jira/browse/JBAS-3652
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ryan Campbell
> Assigned To: Ryan Campbell
> Fix For: JBossAS-4.0.5.GA
>
> Attachments: JBossEULA.doc, JBossEULA.pdf, JBossEULA.txt
>
>
> We need to include the attached EULA text file in all "licenses" folders of
> our distributions. It is an umbrella EULA that does not change the
> fact that our source code is open source...it simply applies a little more
> rigor around use of trademarks and logos as well as Export conditions.
> We do not need to retrofit this into existing builds, just new builds on an
> ongoing basis. Ex. JBoss AS 4.0.5 should include it.
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBMESSAGING-287) RemotingTest.testConnectionListener() invalid
by Ovidiu Feodorov (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-287?page=all ]
Ovidiu Feodorov updated JBMESSAGING-287:
----------------------------------------
Fix Version/s: 1.0.1.CR5
Assignee: Ron Sigal (was: Tim Fox)
Fix Version/s: (was: 1.2.0.Alpha1)
> RemotingTest.testConnectionListener() invalid
> ---------------------------------------------
>
> Key: JBMESSAGING-287
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-287
> Project: JBoss Messaging
> Issue Type: Bug
> Components: Tests and Performance
> Reporter: Ovidiu Feodorov
> Assigned To: Ron Sigal
> Priority: Minor
> Fix For: 1.0.1.CR5
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> I commented out that test because I wanted a clean test run for the release and also because I think the test is invalid.
> After the client connects I assume there is a separate thread that renews the lease on server, so even if the main thread sleeps for 5 secs, the client renews its lease and the ConnectionListener doesn't get called. Please verify my assumption and either fix the test or remove it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBMESSAGING-302) Invoking Topic management interface's listMessagesDurableSub()/ listMessagesNonDurableSub() with empty params throws exception
by Ovidiu Feodorov (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-302?page=all ]
Ovidiu Feodorov updated JBMESSAGING-302:
----------------------------------------
Fix Version/s: (was: 1.2.0.Alpha1)
Assignee: Clebert Suconic
Fix Version/s: 1.0.1.CR5
> Invoking Topic management interface's listMessagesDurableSub()/ listMessagesNonDurableSub() with empty params throws exception
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBMESSAGING-302
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-302
> Project: JBoss Messaging
> Issue Type: Bug
> Components: Configuration and Management
> Reporter: Ovidiu Feodorov
> Assigned To: Clebert Suconic
> Priority: Minor
> Fix For: 1.0.1.CR5
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> 9:18:53,568 ERROR [[HtmlAdaptor]] Servlet.service() for servlet HtmlAdaptor threw exception
> ava.lang.NumberFormatException: For input string: ""
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:424)
> at java.lang.Long.valueOf(Long.java:518)
> at sun.beans.editors.LongEditor.setAsText(LongEditor.java:24)
> at org.jboss.util.propertyeditor.PropertyEditors.convertValue(PropertyEditors.java:260)
> at org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:239)
> at org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
> at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:54)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:173)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
> at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
> at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months