"OTK client update assertion" does not update record in database

Products

• CA API Gateway

Issue/Introduction

We are using the encapsulated assertion 'OTK Client Update' to update a client custom field, sometimes though the update is applied correctly but when checking the client it seems that the field is not updated correctly in the database 

I noticed that if I open the Oauth Manager and refresh the page as soon as the update goes it is registered, while if i don't refresh it manually sometimes it loses the update.

Resolution

The problem is not the "OTK client update assertion" , the problem is the 30 sec caching in the OTK Client get encapsulated assertion used to get the current data from database .

The solution could be is to create a custom encapsulated assertion for otk client db get which does not do the caching

or include a section in the update client policy which is writing the update  also to the cache entry for this record  .