Multiple Conditions -- expiring-password-intercept-config.xml

[Losen, Stephen C (scl)]

Hi Joshua,

You could convert expiring-password.vm to a series of #if tests and #parse commands.

#if (condition1)
    #parse(“expiring-password1.vm”)
#elseif (condition2)
    #parse(“expiring-password2.vm”)
#end

This syntax may not be 100% correct, it’s just an illustration.  The view template has access to a bunch of stuff from the IDP, including the user attributes (I think) and the entityID of the SP (relying party). So you can use that info in your conditions.  See the IDP wiki and the distributed velocity view files for examples.

Stephen C. Losen
ITS - Systems and Storage
University of Virginia
scl at virginia.edu<mailto:scl at virginia.edu>    434-924-0640

From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Joshua Brodie
Sent: Wednesday, December 12, 2018 5:33 PM
To: users <users at shibboleth.net>
Subject: Multiple Conditions -- expiring-password-intercept-config.xml

In expiring-password-intercept-config.xml --- is it possible to have multiple conditions -- say

Condition 1 --- go to expiring-password.vm

Condition 2 --- go to expiring-password2.vm (which we can create)?

Rationale: We have a number of departments who wish different messaging on pages.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20181212/9674f3e7/attachment.html>