• Okta Sign-On Policy

Install Postman and configure the environment for the Okta org that is being modified. For guidance on how to do so, please check the following document: Instructions for the Installation and Configuration of Postman.

In this video, learn how to configure persistent cookie sessions for end users using Postman.

To ensure that end users are not prompted for credentials after the current Okta session is closed, this setting can be applied to the sign-on policy. The following steps should be followed to achieve this:

1. Use the API call GET {{url}}/api/v1/policies?type=OKTA_SIGN_ON to retrieve all policies. Copy and save the policyId as it will be needed for the next API call.

2. Use the API call GET {{url}}/api/v1/policies/{{policyId}}/rules to obtain the ruleId associated with the policy. Save the ruleId.

3. Use the API call PUT {{url}}/api/v1/policies/{{policyId}}/rules/{{ruleId}} to update the policy and rule with the necessary settings. Pay particular attention to the values of the maxSessionIdleMinutes and maxSessionLifetimeMinutes. Before making the call, copy and paste the following JSON in the body and adjust it as required:

   {
     "name": "Sign-On Policy Rule",
     "type": "SIGN_ON",
     "actions": {
       "signon": {
         "access": "ALLOW",
         "requireFactor": false,
         "primaryFactor": "Primary Factor of the Sign-On Policy (that is, PASSWORD_IDP)",
         "rememberDeviceByDefault": false,
         "session": {
           "usePersistentCookie": true,
           "maxSessionIdleMinutes": 100,
           "maxSessionLifetimeMinutes": 100
         }
       }
     }
   }

    

4. After making the call, a 200 status code will be received.

Related References

• Policy API - Create a policy