Content-Type: text/html I stand corrected. Carl is right! In Sentinel V4 you have to return to a static URL. And I have not yet tried passing a query string to the login page and handling it in a non-visual page. The Sentinel authenticated application I was thinking of still uses Sentinel V2. bob From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of Carl Bussema III Sent: Thursday, March 22, 2012 3:43 PM To: Kriegel, Robert Subject: Re: Feature Request I thought Sentinel required a single static "return URL" -- so you always redirect back to page X after a successful login (that said, you could use Cookies, and I suggested that to Jade directly). Can you pass a return URL parameter to the login page? Then I could see doing what you suggest. Carl Bussema III Information Technologist Michigan State University Outreach & Engagement Phone: (517) 353-8977 * Fax: (517) 432-9541 [log in to unmask][log in to unmask]> On Thu, Mar 22, 2012 at 3:26 PM, Kriegel, Robert <[log in to unmask][log in to unmask]>> wrote: Hi Jade, Yes! The easiest way to deep link into a combined public/private application is to pass the needed parameters on a query string. These can be encrypted if database foreign keys or other sensitive data is being passed. Typically, you do not need to store entire application state; but you do need to be able to recover the page state from the query string. I am currently doing this in two different enterprise-level, ecommerce ColdFusion 9 applications. One of these uses Sentinel v4 authentication; the other uses LDAP authentication against Windows Server 2008 domain accounts. If CAFÉ participants are interested, I would be happy to talk about these in a future WEBDevCAFÉ meeting. Robert Kriegel Systems Analyst II ANR Technology Services Agriculture Hall 446 W. Circle Drive, rm 221 Michigan State University East Lansing, MI 48824 phone: 517.353.4890 ext. 169 fax: 517.353.5341 From: Freeman, Jade [mailto:[log in to unmask][log in to unmask]U.EDU>] Sent: Wednesday, March 21, 2012 4:56 PM To: [log in to unmask][log in to unmask]> Subject: Re: Feature Request I don't want to hijack the thread but one of my frustrations with Sentinel is that as it is difficult to do mid-step authentication. In other words, your user is 10 screens into an application and you want to let them know that if they login and are authorized, they would be able to see more, secured, information. To make this work with Sentinel, as the developer you have to develop a mechanism to store complete application state so that when you return from the Sentinel login, you can take them back to the exact same spot in the application as they were only now showing the secured information. For applications that are entirely secured (you must login to access any part of the application), this isn't really a problem but for applications that offer a mix of public and secured functions / information, this is more difficult. It would be nice if there was a way to use Sentinel to authenticate users in this type of workflow. Has anyone found a way to do this?