We have created an application that uses the offline mobile app for iOS. When a user starts to work with it, two requestors are created, one of type APP and one of type BROWSER. When the user closes the app (for example by swiping it away), the APP requestor is cleaned up after 5 mins, but the BROWSER requestor - showing "disconnected" - is never removed. When the user has repeated this several times, he ends up with a whole set of BROWSERs, and the system is filling up rapidly. For this reason we have to restart the whole system every few weeks, which is highly undesirable.
When we create a BROWSER session through the web interface, all works fine: the requestor is removed after 5 minutes. We have properly set the DSS timeout settings to 300 seconds.Our assumption is that it has something to do with the offline app.
What can we do about it?
***Edited by Moderator: Pooja Gadige to add platform capability tag***
@RobertJanStreng That has been a product defect which has been fixed on Pega 8.3.6+, 8.4.5+ and 8.5.3+ patch versions of the Pega Platform.
If applying the newest patch version is not an option - there is a workaround for the issue. Please find the OAuth 2.0 Client Registration instance associated to the Mobile Channel Interface you build the mobile app from (there are two instances of client registrations for each mobile interface - please select the one without `Preview` name in it) and change the refresh token lifetime value to some smaller value. Before the fix has been made - BROWSER requestors created via mobile app had it's lifetime strictly associated with the refresh token lifetime - if I am not mistaken by default that something around 2 weeks.