On 07/05/2015 01:08 AM, Matt . wrote:
> Hi Guys,
> 
> I created a bug where no response is on yet for a week, so I thought
> to ask the mailinglist if someone has seen this behaviour.

Hi Matt,

Sorry for the delay in the answer in Bugzilla, most of the team is now very
busy with FreeIPA 4.2 finalization, so the responses are slower.

In your case, I think we will need more data anyway, specifically what does it
mean that >>The password of a user is randomly "not working"<<.

If password reset is not behaving as it should, we will need full user entry
*before* password reset ("ipa user-show USER --all --raw"), full user entry
*after* password reset and password policy setting for the user ("ipa
pwpolicy-show").

> https://bugzilla.redhat.com/show_bug.cgi?id=1236322
> 
> 
> Description of problem:
> 
> The password of a user is randomly "not working" anymore and needs a
> reset of the password.
> 
> The user is added as passSyncManagersDNs entry and when this user sets
> a password for another user the expire is set to 2035, it does the
> same for itself.
> 
> 
> Version-Release number of selected component (if applicable):
> 
> 4.1
> 
> 
> How reproducible:
> 
> Add a user to passSyncManagersDNs like described here:
> 
> https://docs.fedoraproject.org/en-US/Fedora/15/html/FreeIPA_Guide/pass-sync.html
> 
> 
> Steps to Reproduce:
> 1. Add user to passSyncManagersDNs
> 2. Reset this user his password, login and set the same password again
> so ti stays the same until 2035
> 3. Wait for some days and try to login as this user the password is
> expired or damaged but still says in the GUI it expires in 2035
> 
> Actual results:
> 
> The password expires it get's currupted or so ?
> 
> 
> Expected results:
> 
> It should not expire until 2035!
> 
> 
> 
> I hope someone has a clue here as I can't get anything logged about it.
> 
> Thanks,
> 
> Matt
> 

-- 
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project

Reply via email to