Recently I switched on all DBG logging and now have some strange SQL call for EVERY api call I am doing:
[11:03:29 DBG] CreateContentTypeRequest/hasContentBody:True:POST:application/json:47:
[11:03:29 DBG] SQL: SELECT "Id", "UserAuthId", "Environment", "KeyType", "CreatedDate", "ExpiryDate", "CancelledDate", "Notes", "RefId", "RefIdStr", "Meta" FROM "auth"."ApiKey" WHERE "Id" = @Id
PARAMS: Id=eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6InF5bCJ9.eyJpc3MiOiJzc2p3dCIsInN1YiI6NiwiaWF0IjoxNTY3NTExNTE5LCJleHA<tranceted-bearer-token>
So it is trying to use the bearer-token to check whether this is a valid API key.
Is this something new, or was it there all the time, and is it actually necessary?