Opaque access token structure change after OTK upgrade

Products

• CA API Gateway

Issue/Introduction

Before the upgrade access token 32 characters

DEV 1: "access_token":"b7c045e8-96d6-4650-9562-216e79676a4e"

Policy used for Access token : OTK Generate OAuth Token

After upgrade access token 45 characters

Dev 1: "access_token":"6df0f4b5-587d-4ee8-aae6-b91f9e570cce-1704215545"

Policy used for Access token : OTK Generate OAuth Token

 

Environment

gateway 10.1  OTK 4.6.1 OTK 4.6.2

Cause

New feature to improve expired tokens purging by partitioning the tokens table.

Resolution

OTK version 4.6.2 for Oracle OTK DB 

Feature was added to address performance issue with token maintenance (deleting tokens support DB partition)

https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-management-oauth-toolkit/4-6/release-notes.html  

 

OTK version 4.5 for mysql OTK DB Feature was added to address performance issue with token maintenance (deleting tokens support DB partition)

If the increase token size is an issue set the ClusterWideProperty to FALSE to set access token back to 32 characters 

otk.token_include_partition_key = false