Issue #876 has been updated by janet h.
Ok.... what I see is the following:
For a good "submission" of the password from the main page:
0x0000: 4500 0097 aa77 4000 3e06 7dc3 9205 140a E....w@.>.}.....
0x0010: ac12 c204 185b 0185 0717 d6bd 6a56 0fed .....[......jV..
0x0020: 8018 00fa fd93 0000 0101 080a 094a 7f9a .............J..
0x0030: 683d 1837 3061 0201 0466 5c04 3475 6964 h=.70a...f\.4uid
0x0040: 3d68 6f75 7365 722c 6f75 3d50 656f 706c =jdoe,ou=Peopl
0x0050: 652c 6463 3d69 6e74 2c64 633d 626f 756c e,dc=domain,
0x0060: 6465 722c 6463 3d6e 736f 2c64 633d 6564 dc=ed
0x0070: 7530 2430 220a 0102 301d 040c 7573 6572 u0$0"...0...user
0x0080: 5061 7373 776f 7264 310d 040b 7369 782b Password1...sspmain
0x0090: 6669 7665 3d31 31 pagepassword
For the linked change to the 389ds server I see:
0x0000: 4500 0098 2c5d 4000 3e06 fbdc 9205 140a E...,]@.>.......
0x0010: ac12 c204 1861 0185 de27 fc62 6fa1 8a5f .....a...'.bo.._
0x0020: 8018 00fa b7cc 0000 0101 080a 094d d790 .............M..
0x0030: 6840 702e 3062 0201 0366 5d04 3475 6964 [email protected]].4uid
0x0040: 3d68 6f75 7365 722c 6f75 3d50 656f 706c =jdoe,ou=Peopl
0x0050: 652c 6463 3d69 6e74 2c64 633d 626f 756c e,dc=domain,
0x0060: 6465 722c 6463 3d6e 736f 2c64 633d 6564 dc=ed
0x0070: 7530 2530 230a 0102 301e 040c 7573 6572 u0%0#...0...user
0x0080: 5061 7373 776f 7264 310e 040c 6f6e 652b Password1...ssplink
0x0090: 7477 6f3d 336a 6231 password
I notice the submissions are slightly different. The main page uses a
uid=jdoe,ou=People,dc=domain,de=edu0$0 whereas the linked page uses the
submission format uid=jdoe,ou=People,dc=domain,de=edu0%0#.
This could mean nothing, but I'm suspicious since the hash changes but the
password is wrong.
thanks
----------------------------------------
Bug #876: ssp portal email link failing to correctly update 389 directory
server user password
http://tools.lsc-project.org/issues/876
Author: janet h
Status: New
Priority: High
Assigned to:
Category: Self Service Password
Target version: self-service-password-?
Changing a user's 389 directory server password from the main ssp page (version
self-service-password-0.9-1.el5.noarch.rpm) by entering their old LDAP password
works properly and changes the LDAP password in the database. This password
can then be used to login to other LDAP systems.
However, using the $use_tokens = true option and changing a password via the
emailed link, changes the password hash, but doesn't set the new password it
to the inputted value given by the user. The result is that the user can't
use the "changed" password used to access any LDAP sources and it has to be
reset via the 389-ds software.
However, you can use the password set by the password link in the "Old
password" field on the ssp main page to update your password. This process
works and the 389-ds database is updated properly, allowing the user to login
to other LDAP systems. However, from the messages sent during this process I
don't think this was the intention of the email link. It's quite a convoluted
process, and the emailed password change link should simply update the database
password to the inputted value.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://tools.lsc-project.org/my/account
_______________________________________________
ltb-dev mailing list
[email protected]
http://lists.ltb-project.org/listinfo/ltb-dev
