How do I show a custom page when a public user's session times out?
I have a couple of custom portals for use by public users, i.e. they don't have to have sign on credentials for the application. Since their interactions require certain privileges, I wrote custom authentication services to handle this. This all works great.
However, I cannot get session timeouts to work properly. I set a timeout on the access groups involved. I then tried to see what I could get with OOTB functionality by using LDAPAuthenticationTimeout and LogOff. The tracer revealed in both instances that the timeout happened, but in both instances the busy indicator just kept on cycling on the screen. In the trace log for LDAPAuthenticationTimeout, I could see that the activity was being called, but things went nowhere after that with some inexplicable authentication policy errors. Things looked worse for the LogOff activity, because I could see my custom authentication policy was being called again after the timeout processing and this was then failing.
I then tried to roll my own custom timeout activity:
At least this resulted in a new page being displayed:
I have a couple of custom portals for use by public users, i.e. they don't have to have sign on credentials for the application. Since their interactions require certain privileges, I wrote custom authentication services to handle this. This all works great.
However, I cannot get session timeouts to work properly. I set a timeout on the access groups involved. I then tried to see what I could get with OOTB functionality by using LDAPAuthenticationTimeout and LogOff. The tracer revealed in both instances that the timeout happened, but in both instances the busy indicator just kept on cycling on the screen. In the trace log for LDAPAuthenticationTimeout, I could see that the activity was being called, but things went nowhere after that with some inexplicable authentication policy errors. Things looked worse for the LogOff activity, because I could see my custom authentication policy was being called again after the timeout processing and this was then failing.
I then tried to roll my own custom timeout activity:
At least this resulted in a new page being displayed:
But I am unable to control this page. No matter what I try with different HTML rules, this is the page that always displays.
Hence my question: how can I get a my custom timeout page to display here? Preferably with a "start over" link?
By the way, I searched the community sites, but couldn't find any information that was useful. Most of the information was for much older versions anyway.
***Edited by Moderator: Pallavi to update platform capability tags and add SR details***
Accepted Solution
Updated: 30 Apr 2020 5:56 EDT
Ernst & Young
ZA
The SR has been resolved. If you have a custom authentication activity and wish to have a custom timeout activity with a custom page that displays when there is a timeout, then this is what you need to do:
1) Specify the OOTB timeout activity AuthenticationLDAPTimeout like this:
The Pega support person showed me that if I use this one then I can customise the screen that shows at timeout. If your requirement is different then you may need to experiment with one of the other OOTB activities.
2) Specifiy a custom timeout screen like this:
The HTML Rule @baseclass.CustomerEnrollWebTimeout is my timeout screen and it needs to be in a ruleset that is accessible by the operator access group and role. Mine is called AppUnauthenticated.
In my case the client wanted to display a simple message to indicate that the session timed out with a link that the user can click on to restart the session. I did a save-as of one of the OOTB rules which ended up looking like this:
The SR has been resolved. If you have a custom authentication activity and wish to have a custom timeout activity with a custom page that displays when there is a timeout, then this is what you need to do:
1) Specify the OOTB timeout activity AuthenticationLDAPTimeout like this:
The Pega support person showed me that if I use this one then I can customise the screen that shows at timeout. If your requirement is different then you may need to experiment with one of the other OOTB activities.
2) Specifiy a custom timeout screen like this:
The HTML Rule @baseclass.CustomerEnrollWebTimeout is my timeout screen and it needs to be in a ruleset that is accessible by the operator access group and role. Mine is called AppUnauthenticated.
In my case the client wanted to display a simple message to indicate that the session timed out with a link that the user can click on to restart the session. I did a save-as of one of the OOTB rules which ended up looking like this:
<html>
<head>
<base target="_self">
<title>
<pega:lookup property="pxRequestor.pyCaption" value="Your session timed out" />
</title>
<style>
</style>
<pega:choose>
<pega:when test="true == false">
</pega:when>
<pega:otherwise>
<pega:save name="servURL" appendRef="pxRequestor.pxReqContextURI"/>
<pega:save name="servURL" append="/IAC"/>
</pega:otherwise>
</pega:choose>
<script>
(function () {
var cookies = document.cookie.split("; ");
for (var c = 0; c < cookies.length; c++) {
var d = window.location.hostname.split(".");
while (d.length > 0) {
var cookieBase = encodeURIComponent(cookies[c].split(";")[0].split("=")[0]) + '=; expires=Thu, 01-Jan-1970 00:00:01 GMT; domain=' + d.join('.') + ' ;path=';
var p = location.pathname.split('/');
document.cookie = cookieBase + '/';
while (p.length > 0) {
document.cookie = cookieBase + p.join('/');
p.pop();
};
d.shift();
}
}
})();
</script>
</head>
<body>
<p>Your session timed out. Click <a target="_top" href='<pega:reference name="$save(servURL)" />'>here</a> to go back</p>
</body>
</html>
The script part deletes all existing cookies which is needed to get a new session started once the user clicks on the link. This works for us.
Perhaps one of the Pega experts can cast a wry eye over this and let me know if there is some bad practice(s) been followed here by me.
Accepted Solution
Updated: 30 Apr 2020 5:56 EDT
Ernst & Young
ZA
The SR has been resolved. If you have a custom authentication activity and wish to have a custom timeout activity with a custom page that displays when there is a timeout, then this is what you need to do:
1) Specify the OOTB timeout activity AuthenticationLDAPTimeout like this:
The Pega support person showed me that if I use this one then I can customise the screen that shows at timeout. If your requirement is different then you may need to experiment with one of the other OOTB activities.
2) Specifiy a custom timeout screen like this:
The HTML Rule @baseclass.CustomerEnrollWebTimeout is my timeout screen and it needs to be in a ruleset that is accessible by the operator access group and role. Mine is called AppUnauthenticated.
In my case the client wanted to display a simple message to indicate that the session timed out with a link that the user can click on to restart the session. I did a save-as of one of the OOTB rules which ended up looking like this:
The SR has been resolved. If you have a custom authentication activity and wish to have a custom timeout activity with a custom page that displays when there is a timeout, then this is what you need to do:
1) Specify the OOTB timeout activity AuthenticationLDAPTimeout like this:
The Pega support person showed me that if I use this one then I can customise the screen that shows at timeout. If your requirement is different then you may need to experiment with one of the other OOTB activities.
2) Specifiy a custom timeout screen like this:
The HTML Rule @baseclass.CustomerEnrollWebTimeout is my timeout screen and it needs to be in a ruleset that is accessible by the operator access group and role. Mine is called AppUnauthenticated.
In my case the client wanted to display a simple message to indicate that the session timed out with a link that the user can click on to restart the session. I did a save-as of one of the OOTB rules which ended up looking like this:
<html>
<head>
<base target="_self">
<title>
<pega:lookup property="pxRequestor.pyCaption" value="Your session timed out" />
</title>
<style>
</style>
<pega:choose>
<pega:when test="true == false">
</pega:when>
<pega:otherwise>
<pega:save name="servURL" appendRef="pxRequestor.pxReqContextURI"/>
<pega:save name="servURL" append="/IAC"/>
</pega:otherwise>
</pega:choose>
<script>
(function () {
var cookies = document.cookie.split("; ");
for (var c = 0; c < cookies.length; c++) {
var d = window.location.hostname.split(".");
while (d.length > 0) {
var cookieBase = encodeURIComponent(cookies[c].split(";")[0].split("=")[0]) + '=; expires=Thu, 01-Jan-1970 00:00:01 GMT; domain=' + d.join('.') + ' ;path=';
var p = location.pathname.split('/');
document.cookie = cookieBase + '/';
while (p.length > 0) {
document.cookie = cookieBase + p.join('/');
p.pop();
};
d.shift();
}
}
})();
</script>
</head>
<body>
<p>Your session timed out. Click <a target="_top" href='<pega:reference name="$save(servURL)" />'>here</a> to go back</p>
</body>
</html>
The script part deletes all existing cookies which is needed to get a new session started once the user clicks on the link. This works for us.
Perhaps one of the Pega experts can cast a wry eye over this and let me know if there is some bad practice(s) been followed here by me.