You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A dev might have logged into another Org, and used the logged-in access token (from the web browser) to do operations on their current Project. This is a mismatch, and results in an error when accessing certain operations.
Error
$ aio console project list
» Error: [CoreConsoleAPISDK:ERROR_GET_PROJECTS_BY_ORG_ID] 403 - Forbidden
» ({"id":"f43a63e9-a891-4b53-9416-2a83c55aa08b","messages":[{"template":"ERR_MSG_OPERAT » ION_NOT_ALLOWED","message":"User [REDACTED_USER] » not allowed to access resources of org [REDACTED_ORG_ID]"}]})
Investigation
The Org Code from running aio console org ls does not match the Org Code when running aio config get project.org.ims_org_id.
This value is in the .aio file of the project.
The fix is above, but for diagnostic purposes, there should be a command, or a flag to a command, that can show there is an Org Code mismatch, thus the dev needs to login again via the Resolution step above. Perhaps it is a good candidate for aio info
The text was updated successfully, but these errors were encountered:
shazron
changed the title
Add a verification check on access token, whether it is the correct one for the project
Add a verification check on Org Code, whether it is the correct one for the project
Jun 24, 2024
A dev might have logged into another Org, and used the logged-in access token (from the web browser) to do operations on their current Project. This is a mismatch, and results in an error when accessing certain operations.
Error
Investigation
The Org Code from running
aio console org ls
does not match the Org Code when runningaio config get project.org.ims_org_id
.This value is in the
.aio
file of the project.An access token is tied to a specific Org.
Resolution
aio logout --force
aio login
Then run your command again.
Diagnostic Fix
The fix is above, but for diagnostic purposes, there should be a command, or a flag to a command, that can show there is an Org Code mismatch, thus the dev needs to login again via the
Resolution
step above. Perhaps it is a good candidate foraio info
The text was updated successfully, but these errors were encountered: