Incompatibility between recovery password and user-reminder

Hello, When we use recovery password, we cannot user user-reminder on this user because he already have a token that exist.

The idea is to store in FusionDirectory another branch for the user-reminder's token.

Cheers.

(from redmine: issue id 5264, created on 2016-11-29, closed on 2016-12-08)

• Relations:
  • copied_to #5267
  • copied_to #5273
• Changesets:
  • Revision 3046a08e by Benoit MORTIER on 2016-12-02T14:48:18.000Z:

Fixes: #5264 Incompatibility between recovery password and user-reminder

Added the new fdReminderTokenRDN

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

• Revision e702ad9f by Benoit MORTIER on 2016-12-02T15:07:33.000Z:

Fixes: #5264 Incompatibility between recovery password and user-reminder

only putting ou=reminder in the attributes

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

• Revision 90897a82 by Benoit MORTIER on 2016-12-07T09:10:09.000Z:

Fixes: #5264 Incompatibility between recovery password and user-reminder

Added the new fdReminderTokenRDN

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

• Revision 7eb2875a by Benoit MORTIER on 2016-12-07T09:10:16.000Z:

Fixes: #5264 Incompatibility between recovery password and user-reminder

only putting ou=reminder in the attributes

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

• Custom Fields:
  • Bug in version: 1.0.17
  • Support contract: Silver

hello,

yes they are stored in the same branch and in the same format with the same attributes so the clash is impossible to avoid. i propose we use the ReminderTokenRDN and RecoveryTokenRDN to have correctly structured branches for them.

should they be inside the tokenRDN branch ?

Cheers

(from redmine: written on 2016-11-29)

Close issue

(from redmine: written on 2016-12-08)

closed

added Changed label