SpacyNG / pwm

Automatically exported from code.google.com/p/pwm
0 stars 0 forks source link

User can get placed into a "half activated" state #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. User begins account activation and successfully completes stage 1
2. Users "activated" flag is set.
3. User allows their session to timeout before setting a password.
4. Password is still set to the temp value generated by PWM.
5. User is stuck with a useless account.

What is the expected output? What do you see instead?
PWM verify that FULL activaction took place before setting the activated 
attribute? Remove temporary password if user is hald activated.

What version of the product are you using? On what operating system?
PWM 1.5.1 redhat linux el5.4 + tomcat6

Please provide any additional information below.

Original issue reported on code.google.com by sea...@gmail.com on 23 Aug 2010 at 6:32

GoogleCodeExporter commented 9 years ago

Original comment by jrivard on 23 Aug 2010 at 10:05

GoogleCodeExporter commented 9 years ago
This should be resolved as of b994.  The user activation write attributes will 
not actually be written to the user until after the password is modified.

Original comment by jrivard on 11 Oct 2010 at 3:03