After deploy/rollback related to tenant admin, user can't login using context (tenant) admin
Description
CAPL - Bug default text according to the team DoR (Definition of Ready)
01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
02 - PROBLEM (WHAT'S THE ISSUE?):
After rollout that happened on 06/05 at 22 brt the following user can’t login using the following parameters. It is running the login without issues on our UI flow (tenant fluigdata same as admin).
curl 'https://api.carol.ai/api/v1/oauth2/token' -H 'accept: application/json' -H 'content-type: application/x-www-form-urlencoded' --data 'grant_type=password&username=robson.poffo%40totvs.com&password=PASSWORD_HERE&subdomain=admin&applicationId=0a0829172fc2433c9aa26460c31b78f0&connectorId=0a0829172fc2433c9aa26460c31b78f0' --compressed
Returns:
{"applicationErrorCode":null,"errorCode":401,"errorMessage":"Incorrect login was used.","possibleResponsibleField":"userLogin"}
This incident impacted the SQL Processing tasks.
More details about this issue here: https://totvslabs.slack.com/archives/CBSRDV2V9/p1686109463838839?thread_ts=1686073968.730819&cid=CBSRDV2V9
Describing other impacts.
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT):
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):
- Understand what happened and if it is something we need to consider on our migrations.