IFS Middleware Server Admin console Access is needed to perform this change.

Please note there is a system wide impact due to this change. We strongly recommend that you do this change to a TEST environment first and check the performance.

For this to be done, one must use IFS Middleware Server Admin Console. System admin should have access to this.

Note : Following steps applies to managed servers in Main Cluster.

1. Go to IFS Middleware Server Admin Console

2. Login with credentials

3. Go to Main Cluster -> Managed Servers

4. Go to CONFIGURATIONS tab – This is the place to configure cluster wide configurations

5. Under Server Startup, you will find Arguments: section. In the input field, you should set following argument (put a space in front if there are arguments set already)

-Difs.oidc.refreshtoken.lifetime=108000

Numeric value given here represents 0.5 hours’ time in seconds, please change accordingly.

6. Save changes using save button (top left-hand corner)

7. Go to SERVERS tab and press Restart ALL. Which is found in top tools bar. This will restart all servers under Main Cluster.

This will result in extended refresh token lifetimes for Main Cluster.

*You may want to use same setting for Integration Cluster too. For that, perform same steps through Integration Cluster menu.*

---

@VinuP do you know what the default value is and what some of the impacts might be that we need to consider? 

---

Hello @PIINKADAM,

You can find that information in the technical documentation in the following link. Default value for the latest update is now 172800 seconds (2 days).:

https://docs.ifs.com/techdocs/foundation1/040_administration/210_security/015_authentication/040_configure_DBIDP/default.htm#Configure_behaviour_through_startup_paramters
 

Thanks and Best Regards,

Ibrahim

---

Thanks @Ibrahim Naazir. If this value is already 2 days what scenario would require extending it further? We currently have issues where the users get a Sync is failing error and the recommendation is to extend this value.

---

Hello @PIINKADAM,

Difficult to say why it was recommended. Do you have more information about this sync is failing? Is it asking you to login to the application? Adjusting these values will determine how long will the app force the user to log back in is what I am guessing. It is the lifetime value for the refresh token and once this is expired, the system will consider the session invalid. The lower this value the more frequently you will have to log back into the application and by login I dont mean entering a PIN but your actual username and password.

Thanks and Best Regards,

Ibrahim

---