When I access the OOTB portal without logging in, I am redirected to the login screen.
Where is this controlled?
I have implemented a custom widget (icon link), but when I click it without logging in, the login screen does not appear.
Does any special configuration need to be done?
The custom widget is set to link to a custom page.
Maybe the page is configured so that the login screen appears even when I'm not logged in?
<OOTB>
↓
Hi @bonsai
Example
Navigate to Service Portal > Pages.
Find the page you are trying to access (e.g., the default OOTB homepage).
Note : To find Home page of Portal Navigate to Service Portal > Portals and open your portal record and check for Homepage field as shown below
If the page is "Public" (as shown below) checkbox is not checked, an unauthenticated user will be automatically redirected to the portal's login page. This is the out-of-the-box (OOTB) behavior for most pages that require a user to be logged in.
You have a custom widget that is linking to a custom page.
Check is your custom page is set to "Public" (or is not restricted) and therefore does not trigger the login redirect when an unauthenticated user accesses it.
The system allows the unauthenticated user to land on the page, but the widgets on that page are not configured to be public (as show below) and fail to load their data, leaving you with a blank or incomplete page.
In your case The Target Page is should NOT Public: Navigate to Service Portal > Pages and find your custom page that your widgets to. Uncheck the "Public" checkbox.
If this helped to answer your query, please mark it helpful & accept the solution.
Regards,
Krishnamohan
Hi @bonsai
Example
Navigate to Service Portal > Pages.
Find the page you are trying to access (e.g., the default OOTB homepage).
Note : To find Home page of Portal Navigate to Service Portal > Portals and open your portal record and check for Homepage field as shown below
If the page is "Public" (as shown below) checkbox is not checked, an unauthenticated user will be automatically redirected to the portal's login page. This is the out-of-the-box (OOTB) behavior for most pages that require a user to be logged in.
You have a custom widget that is linking to a custom page.
Check is your custom page is set to "Public" (or is not restricted) and therefore does not trigger the login redirect when an unauthenticated user accesses it.
The system allows the unauthenticated user to land on the page, but the widgets on that page are not configured to be public (as show below) and fail to load their data, leaving you with a blank or incomplete page.
In your case The Target Page is should NOT Public: Navigate to Service Portal > Pages and find your custom page that your widgets to. Uncheck the "Public" checkbox.
If this helped to answer your query, please mark it helpful & accept the solution.
Regards,
Krishnamohan
