Username velocity variable in expiring-password.vm
Cantor, Scott
cantor.2 at osu.edu
Wed Feb 1 14:25:46 EST 2017
On 2/1/17, 2:13 PM, "users on behalf of Darren Struthers" <users-bounces at shibboleth.net on behalf of dstruthers at plu.edu> wrote:
> This does not seem to work in the context of expiring-password.vm.
There are technically two pieces that use that template right. The original one is part of the conditions hook that does run inside the Password flow and could use the same call as the login form. The one added in 3.3 that's an interceptor absolutely cannot, nor can anything else outside the Password method.
> We are attempting to customize the appearance of our expiring password notification and would like the template to
> have access to the username if that is possible. If anyone knows of a way to set a username variable in this context, I'd
> appreciate some insight. We're running IdP 3.3.
For anything running after authenticaton is complete, the principal name and Subject for the request is always inside the SubjectContext child, that's the arbiter of "truth" for the rest of the system.
-- Scott
More information about the users
mailing list