You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2011/04/08 05:54:44 UTC

[jira] Issue Comment Edited: (MRM-1466) LDAP authentication forces "Change Password" even upon authentication success

    [ http://jira.codehaus.org/browse/MRM-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262911#action_262911 ] 

Brett Porter edited comment on MRM-1466 at 4/7/11 10:53 PM:
------------------------------------------------------------

sorry I missed this issue being opened.

this change may have taken effect, but it won't undo the flagging of accounts that require a password change. As an admin, you can go to the user account and uncheck that box if necessary.

That said, I'm not sure why change password would be in effect if you're using LDAP...

      was (Author: brettporter):
    sorry I missed this issue being opened.

this change may have taken effect, but it won't undo the flagging of accounts that require a password change. As an admin, you can go to the user account and uncheck that box if necessary.
  
> LDAP authentication forces "Change Password" even upon authentication success
> -----------------------------------------------------------------------------
>
>                 Key: MRM-1466
>                 URL: http://jira.codehaus.org/browse/MRM-1466
>             Project: Archiva
>          Issue Type: Bug
>          Components: Users/Security
>    Affects Versions: 1.3.4
>         Environment: Linux RHEL 5.5 / Archiva 1.3.4 stand-alone execution
>            Reporter: Adam Chandler
>
> I have a split configuration and for the life of me cannot figure out why Archiva is prompting users to change their passwords upon successful login.  I have set security.policy.password.expiration.enabled=false to no avail.  I have made this change in the split conf area as well as in the security.properties AND security_en.properties under the .../WEB-INF/... area.  Nothing seems to work.  The other values in the security.properties get picked up fine, so I can only assume this is a bug.
> Please let me know what additional information would be useful.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira