Actions
Bug #18808
closed
OIDC token check can fail due to concurrent requests
Story points:
-
Release:
Release relationship:
Auto
Description
If two or more concurrent requests present the same OIDC token, and that token has not already been cached as an Arvados token in the database, multiple threads may try to insert a new token, in which case all but one will fail due to the unique constraint on the api_token column.
user supplied log excerpt:
"respBody":"{\"errors\":[\"error adding OIDC access token to database: pq: duplicate key value violates unique constraint \\\"index_api_client_authorizations_on_api_token\\\"\"]}\n"
In this situation the losing thread should detect the race and use the token that was added by the winning thread, instead of erroring out.
Updated by 
Updated by
Actions