Security Assist - persistence of login
I would have preferred to test this before asking. (And I may have missed something in a tutorial.) But setting up a test, a full test, could disrupt the production site. So, if I might check:
May I get the brief overview regarding persistence of login, with Security Assist?
Let me set the scene, to make clear what is at stake for us.
Our subscribers, weekly - working from an emailed list - repeatedly click "Read more" in that emailed list. Each "Read More" will take them to a site page where they must first log in, to see the information. Almost certainly they will close that site window, before clicking the next "Read more" in the email newsletter.
The question is, will their login persist after they close the window? Of course, we must not be forcing them to login repeatedly, just to get at the rest of the email items.
Security Assist uses a session variable to record the login, as you have taught / we have learned. So it seems the question is, will that session variable expire when the subscriber closes each "Read More" window? or persist …
This leads in general to three related queries, if I may ask:
1 Is there a tidy description of what does 'expire' the session variable?
2 And of course, what keeps it active?
3 Or, is there some mechanism available to manage the persistence?
(We will have a login and a logout page on the site. But users of the weekly email will not typically go to the site itself. That is, except for their trip to each "Read more" page, page by page.
(Perhaps on a related note, am assuming that the subscriber's simple attempt to reach a "Read more" page will trigger the page identified by "WA_Auth_RestrictAccess," thus inviting login. If this latter is incorrect, let's make that a subject for a later support question.)