Hi Sabrina,
I'm aware this is quite old now, but there is a recent query from Katie A about this so I thought I would add our experience.
We have implemented what you describe on our Service Portal. Our Portal is a mix of Public and non-Public content, so making $sp inactive in Public Pages is not an option for us. I did this by looking at how Widgets like the OOTB Login one worked and using code from there. e.g:
Server Script:
data.default_idp = GlideProperties.get("glide.authenticate.sso.redirect.idp");
if (input && input.action === "set_sso_destination") {
gs.getSession().putProperty("login_redirect_url",'/sp?id=kb_article&sys_id=' + $sp.getParameter('sys_id'));
}
Client Controller:
c.data.url = $window.location.href;
if (!c.data.isvalid && $scope.user.name == 'Guest') {
c.server.get({
action: "set_sso_destination"
}).then(function() {
var url = "login_with_sso.do?glide_sso_id=" + c.data.default_idp;
$window.location.href = url;
});
}
The isValidRecord and canRead checks on the GlideRecord in the Server Script mean that the redirect is only triggered for non-Public articles when the user is not logged in (is 'Guest' user). In addition, this means we can also present a different message to users who login but don't have permissions to view the article.
Hope this is helpful.
Kind regards,
Charlotte
