Add Timeout value to OKTA SSO profile
Nodegrid has default timeout value for all sessions in System::Preferences Session Idle Timeout option. Although, there is a way one can set custom timeout value for service like OKTA.
OKTA is a customizable and secure solution to add authentication and authorization services to your application. While in Nodegrid
there is no way to add timeout value for single user, one can add the timeout value on group level.
Just add the users to specific Group and go to Security::Authorization: :<group>::Profile in WebUI.
Enable Custom Session Timeout option and add the timeout value in seconds. Click Save to save the settings.
This will override the global timeout settings and provides more granular control.
Note: Make sure the individual users are part of the correct group.
Related Articles
How to Configure Okta in Nodegrid
How to configure Single Sign-On authentication in Nodegrid using Okta This document will guide the configuration required in Nodegrid, and Okta. Nodegrid currently supports SP-Initiated SSO, and IdP-Initiated SSO. Create the Nodegrid Application ...
How to configure Nodegrid for OKTA in cluster
Single Sign-on (SSO) enables users to authenticate with multiple applications using only one set of credentials. Nodegrid can also be configured for OKTA in cluster so okta user can login in the coordinator and the user can access the connected ...
How to authorize OKTA groups in Nodegrid
Okta Side: 1. Login to Okta admin panel 2. Navigate to Directory and select People click Add person and enter the name of user and fill the details 3. Navigate to Directory and select Group click Add group and enter the name of group (in my case ...
Single Sign-On (SSO)
What is Single Sign-on? Single Sign-on (SSO) enables users to authenticate with multiple applications using only one set of credentials. After the first authentication, users are then signed in to other applications automatically. With SSO, users ...
Configuring Session Idle Timeout
The idle session timeout is the number of seconds to timeout the open sessions due to inactivity. Changes made will affect the new sessions only, the open sessions which are already in use will continue to follow the timeout value since the start of ...