Experience.FellowshipOne.com

We have successfully gotten the embedded login to correctly authenticate a user with DE, however, when an already logged in user clicks on a weblink popup such as Event Registration, she is prompted to login again in the popup window. I'm guessing that we need to simulate the cookie that the Weblink login writes so that the popup weblinks see that we are already authenticated. Anyone know how to write that cookie? Or is there some other method for telling the weblink to write the cookie for us without the user having to login in twice?

Thanks!

Hey Seth,

A simpler way to do this is to append the iCode to the end of the URL being accessed. The iCode is the unique code for this individual stored in their record. It's returned by DE after successful login. You can parse the returned XML to retrieve it and set it as a session variable.

You can see how the iCode is appended to the end of the URL by using the default WebLink login page. For example, use it to log into Online Giving or Event Registration and then check out the URL.

Appending this code will prevent the WebLink application from asking for re-authentication.

Hi -- just curious how secure this is (not to be critical, just paranoid!).

 I'm concerned about what happens if someone bookmarks a link with the iCode in it, and (say) emails it to someone else.  Would this "automatically" get the second person in as the first, or would it notice the lack of a cookie and log them in?

Thanks!