
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-12-2018 09:48 AM
Hello SN Community-
I see this topic has been addressed a few times but I can't seem to find a proper solution for our situation.
First, we are self hosted.
If a user, with and without a role, hits our site (https://abc.def), they are logged in, which is good. If the user has no roles, they are taken to our /ess page. This is good too.
Now, take that same user who has a role AND a user who has no roles and give them the link https://abc.def/ess.
If they start with a fresh browser, meaning there is no browser open, and they hit the /ess page directly, turns out they are not authenticated/logged in and basically are stuck with a pretty looking ess page but the links on the page will not work. Each link takes them back to the ess homepage. By removing the /ess from the URL, they then taken to the Service Portal, and authenticated/logged in automatically.
Basically what I think I need is a script on the ess portal that checks to see if the user is authenticated/logged in. If they are not logged in, then log them in and send them back to the /ess homepage.
Any feedback is greatly apprecaited
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-05-2018 09:28 AM
Got this figured out. These actions may not apply to folks hosted by SN. We are self hosted.
Our load balancer is Apache HTTPD. Apache checks the client certificate. If the cert is valid, the user is taken to our ESS page if they do not have a role or kept in the internal site if they do have a role.
The first check was the Log In rule 'Users without Roles to ESS'. Ensure this is active. The script should be what came 'out of the box':
!gs.getUser().hasRole();
Change Content page value to your own portal page
The second action was to navigate to sys_public.list
Ensure the following page is active=false: view_content
This information came from: Configure CMS sites for single sign-on (SSO)
The third action was to create a new sys_public page. Set Active = true and page = <name of site>. In our case, the name of our site is 'ess'

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-05-2018 09:28 AM
Got this figured out. These actions may not apply to folks hosted by SN. We are self hosted.
Our load balancer is Apache HTTPD. Apache checks the client certificate. If the cert is valid, the user is taken to our ESS page if they do not have a role or kept in the internal site if they do have a role.
The first check was the Log In rule 'Users without Roles to ESS'. Ensure this is active. The script should be what came 'out of the box':
!gs.getUser().hasRole();
Change Content page value to your own portal page
The second action was to navigate to sys_public.list
Ensure the following page is active=false: view_content
This information came from: Configure CMS sites for single sign-on (SSO)
The third action was to create a new sys_public page. Set Active = true and page = <name of site>. In our case, the name of our site is 'ess'