Requiring Password Change

groov RIO
1

We have a customer reporting that they are getting multiple requests for password change throughout the day. Is there any issue you may be aware of, which would trigger a password change request without the user doing that themselves?

2

I wonder, is the customer using LDAP?
Thatā€™s the only thing that I can think would be nagging to change their password. (And it would be the customer IT dept LDAP settings doing it, not the RIO).
There is no ā€˜timerā€™ or such in RIO or EPIC to ask for a password change. There has been some talk about adding an inactivity auto logout function, but that has not been implemented yet.

3

Not using LDAP. It doesnā€™t make sense to me either, yetā€¦

I could see a customer using different browsers or incognito or something without knowing, and reporting having to login too much, but reports of being asked to change password on the same account is baffling, and with the login changes re:LDAP I thought Iā€™d ask.

If it persists Iā€™ll see about getting a repro. case. Thanks for the response.

4

Any chance you could get some screen shots from the customer when the password change pops up?
That would be really helpful (and interesting) to see where it is coming from - ie, what terms are used.
Even some cell phone photos would be invaluable to track this down.

5

Hereā€™s a foolproof reproduction case:

  1. Request a user change their password on next login (from manage/users)
  2. Have that user login, notice it requires a password change
  3. Have that user log out
  4. Have that user login again. Notice it requires another password change
  5. Repeat 3 & 4 until the user runs out of patience
  6. Manually un-set the ā€œRequire password change on next loginā€ toggle for that user

I believe the intention is to have the ā€œRequire password changeā€ toggle be a one-time thing, but it is persistent. Is that the intended behavior?

1 Like
6

@loren1 Thanks so much for the detailed reply.
Our software engineers have been able to reproduce this and are looking at fixing it asap.

1 Like
7

@loren1 KB is here: Opto22 - KB89890
Fix is in 3.2.2 which is due out in a few days.
Thanks again for your help tracking this one down.

1 Like