Product/components used and version/fix level:
API advanced Gateway 10.3
Internal Data Store is configured in cluster
Detailed explanation of the problem:
Application access tokens do not match across cluster
Error messages / full error message screenshot / log file:
different access tokens are created when propagation application across cluster node
for instance, creating application on the node 1 propagates to node 2 but the access tokens do not match …
how to configure API clients accessing gateways via load balancer ?
Question related to a free trial, or to a production (customer) instance?
licensed, to be upgraded
Kindly elaborate more about your setup ? It seems your question is having very less information.
When you say “creating application on the node 1 propagates to node 2 but the access tokens do not match” ? Ideally your token should also be synced there. Because Both you application and token will be get stored to IDS.
Can you elaborate your setup ? How many gateway and IDS and how IDS cluster setup is ?
Good day Dinesh, thank you very much for your time.
I do fully agree with you on the propagation of the access tokens.
The setup is two AGW nodes and IDS cluster that seems works but not 100%.
Please find this cluster green health check and also replication issues where you see the application mWtech appears only on on server. The second server’ access token is much longer, however after regenerating it’ length matches one on the first server, although the tokens are out of synch.
Note, this is version 10.3, and the issue appears in two environments QA and Production. Perhaps, we must patch this version, or upgrade to 10.11 if the resolution is not found otherwise.
The following fixed the issue:
cloning node1 to node2 with the respective changes in the IDS config and recreating data directory
restarting node2 IS
redeploying API from node1 to node2