How portal visitor authentication works with different type

Posted by ithrees on 24-Jul-2014 03:10

Hi All,

For a rollbase application there is a portal to engage with visitors who can do things like register, update, navigate and login later to update and so. 

As most of the pages are generic pages with lot of customization and few object create pages I am curious to know,

  • How the user credential for the authentication will be shared with every other pages that need user authentication.
  • In case of registration, If the user register with the login name and password how the same user credentials will be used to navigate to other pages which require user authentication.
  • How the timeout will be handled (how to configure timeout value)
  • On a time out, will it require the user to login again and where it will redirect the user, to the last visited page or to the first page
  • How the authentication will be applied, only for the current user object record and its related object’s records..? 

Thank you in advance.

All Replies

Posted by Orchid Corpin on 28-Jul-2014 12:45

Hi Ithrees,

Here are the answers for the following questions.

Q: How the user credential for the authentication will be shared with every other pages that need user authentication.

A: To do this edit the pages, in the script component or HTML Component select the “Current Visitor” (for non-USER object) in the first drop down menu and in the second drop down menu you can see related info once the user has already logged in.

Using USER object as portal visitor you can see information of the current logged in user in both “Current Visitor and Current User” drop down.

Q: In case of registration, If the user register with the login name and password how the same user credentials will be used to navigate to other pages which require user authentication.

A: If the pages has the properties of “Only logged in portal visitors can access this page” there will be no problem navigating to other pages once the user has successfully registered and logged in, the first answer above maybe use to display information of the current user / visitor to all pages.

Q: How the timeout will be handled (how to configure timeout value)

A: Portal session timeout can be configure via tomcat for private cloud's local file > conf > web.xml > node <session-timeout>. The default timeout is 30 minutes. 

Q: On a time out, will it require the user to login again and where it will redirect the user, to the last visited page or to the first page

A: User will be redirected the last visited page after logged in.

Q: How the authentication will be applied, only for the current user object record and its related object’s records..? 

A: You can create a new list view with the filtering of the object with Portal user equals to “Current Visitor” (Image 1) and in the portal set the “Use List View” with the filter for current visitor only (Image 2).

Image 1. 

Image 2. 

Hope this will help.

Regards,

Orchid

Posted by ithrees on 06-Aug-2014 02:50

Hi Orchid,

It's really helpful, Thank you so much.

This thread is closed