Since OAuth 2.0 tokens are stored in a persistent layer (via a token data provider plugin), regular database maintenance is necessary. It is recommended to configure a regularly executed OAuth 2.0 clean up task in the Service Container.
In fail over and load balancing scenarios, all Airlock IAM instances must share the persistency layer. Otherwise OAuth 2.0 state information will be lost when switching instances.