[11:23:38 CDT(-0500)] <athena> ok, so i've been thinking about the password reset a bit more
[11:23:51 CDT(-0500)] <athena> guess maybe we could implement it just for local accounts
[11:24:04 CDT(-0500)] <athena> and it probably won't have enough of an API yet to be easily translatable to non-local
[11:24:21 CDT(-0500)] <athena> but at least the UI and such will be there, and maybe we can make it easier to implement for LDAP/whatever later?
[11:24:42 CDT(-0500)] <EricDalquist> yup
[11:25:00 CDT(-0500)] <athena> so for the local implementation
[11:25:15 CDT(-0500)] <athena> thinking maybe we add a new attribute that's just "loginToken" or something liek that
[11:25:41 CDT(-0500)] <athena> the self-service portlet's original implementation actually overloaded the password to be a login token - was prefaced by something that wasn't an SHA or whatever
[11:25:52 CDT(-0500)] <athena> but thinking it'd be more clear to not do that and create a new attribute
[11:26:12 CDT(-0500)] <athena> then when a password was reset we could null out the current password and set that login token? maybe even provide a login token date?
General
Content
Integrations