Access user attribute in terms-of-use.vm

[Rhian Resnick]

Thank you that makes complete sense.


We could then have a relaying party policy applied on the destination site that does not initiate that flow during authentication?


Rhian Resnick

Assistant Director Middleware and HPC

Office of Information Technology


Florida Atlantic University

777 Glades Road, CM22, Rm 173B

Boca Raton, FL 33431

Phone 561.297.2647

Fax 561.297.0222

 [image] <https://hpc.fau.edu/wp-content/uploads/2015/01/image.jpg>

________________________________
From: users <users-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Friday, August 18, 2017 12:46:30 PM
To: Shib Users
Subject: Re: Access user attribute in terms-of-use.vm

On 8/18/17, 10:56 AM, "users on behalf of Rhian Resnick" <users-bounces at shibboleth.net on behalf of rresnick at fau.edu> wrote:

> I spent a few minutes searching the manual and would appreciate a description of redirecting and coming back. That could result
> in a more elegant solution.

A flow definition can start with a view-state that "renders" itself via an external redirect:

    <view-state id="ExternalTransfer" view="externalRedirect:https://www.example.org/tou?return=...">
       <transition to="proceed" />
    </view-state>

The parameter you would have to pass over to get back would be a URL encoded copy of the expression:

flowExecutionUrl + '&_eventId_proceed=1

flowExecutionUrl is a built-in flow variable that will carry the whole URL back plus the flow execution key parameter (e1s2, whatever), and you add the parameter there to trigger the flow to move along.

That's just a rough outline.

Obviously there's no existing interceptor that's just doing this. That would be easy to add as a built-in example, just have an interceptor that does nothing but pass control out and back in with a config bean to control where to send it.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170821/45c729de/attachment-0001.html>