[JBoss JIRA] Updated: (JBAS-2681) Add real support for password-stacking (useFirstPass) in LDAPExtLoginModule
by Seth Wilcox (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2681?page=all ]
Seth Wilcox updated JBAS-2681:
------------------------------
Attachment: LDAPAuth.patch
Fixes unexpected behavior with LdapExtLoginModule when using the password-stacking
> Add real support for password-stacking (useFirstPass) in LDAPExtLoginModule
> ---------------------------------------------------------------------------
>
> Key: JBAS-2681
> URL: http://jira.jboss.com/jira/browse/JBAS-2681
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: All
> Reporter: Didier Kreutter
> Attachments: LDAPAuth.patch
>
>
> It would be nice, we could use the "useFirstPass" option of this login-module, like it can be done with the DatabaseServerLoginModule.
> With the construct of the LDAPExtLoginModule, it is not possible to use the LDAP-Directory to search for Roles without having to validate the Password, if this has been done by an precedent LoginModule (DB or SSO).
> I think the problem is in the fact, that the effective Role-Search is done in the overridden "validatePassword" function... witch will never been called when the "useFirstPass" option is set. Is it Possible to fulfill the roles in the getRoleSets() function?
--
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
18 years, 9 months
[JBoss JIRA] Updated: (JBMESSAGING-381) Add param on destination to disable persistence
by Jeff Mesnil (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]
Jeff Mesnil updated JBMESSAGING-381:
------------------------------------
Attachment: patch-JBMESSAGING-381.txt
2nd version of the patch.
removed a nasty bug in the test which kept old references on ConnectionFactory (after server restart) making all over subsequent local tests fail...
> Add param on destination to disable persistence
> -----------------------------------------------
>
> Key: JBMESSAGING-381
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
> Project: JBoss Messaging
> Issue Type: Feature Request
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Fix For: 2.0.0 Beta 1
>
> Attachments: patch-JBMESSAGING-381.txt
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.
--
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
18 years, 9 months