Receiving 403 error on Admin Console after successful login

[echoari77]

Hi team,
I'm encountering an issue where I can successfully reach the digiRunner Admin Console login page and enter my credentials. However, immediately after logging in, I'm presented with a 403 Forbidden error.

Here are the details from the response:
Http Codes : 403
Url : https://[ip]:[port]/dgrv4/tptoken/oauth/token
Response : {
"headers": {
"normalizedNames": {},
"lazyUpdate": null
},
"status": 403,
"statusText": "OK",
"url": "https://[ip]:[port]/dgrv4/tptoken/oauth/token",
"ok": false,
"name": "HttpErrorResponse",
"message": "Http failure response for https://[ip]:[port]/dgrv4/tptoken/oauth/token: 403 OK",
"error": {
"timestamp": 1741161657929,
"status": 403,
"error": "Forbidden",
"message": "YWRtaW5Db2525zb2xl' Client(application) disable",
"path": "/oauth/token"
}
}

The error message within the response body states: "YWRtaW5Db2525zb2xl' Client(application) disable". It looks like something related to the client application being disabled.
Could you please provide some guidance on how to troubleshoot and resolve this 403 Forbidden error?
Thanks in advance for your help!

[TPIsoftwareOSPO]

Hi @Annawu0301 ,

Thanks for providing such detailed information. The error message "YWRtaW5Db2525zb2xl' Client(application) disable" is indeed the key here. This specific 403 error indicates that the default adminConsole client (application) used for accessing the Admin Console has been disabled.

This typically happens if the adminConsole client's status was changed to disabled.
Here's how to check and resolve it:
First, you can execute the following SQL query to check the current status of the adminConsole client in your database:

SQL
select * from tsmp_client tc where client_name ='adminConsole';

If theCLIENT_STATUSreturned in the query result is 2, then it confirms that this is indeed the cause of your issue.
A CLIENT_STATUS of 2 means the client is disabled.
To re-enable the admin Console client and resolve the 403 error, execute the following SQL command:

SQL
update tsmp_client set client_status='1' where client_name ='adminConsole';

After executing this UPDATE statement, try logging into the Admin Console again. The CLIENT_STATUS of 1 means the client is enabled.
Important Note:

● If you still have other user accounts that can log into the Admin Console, you can log in with one of those accounts and navigate to the client management section to enable the adminConsole client through the UI.
● However, if no other accounts can log in, then direct database modification as described above is necessary.

Let us know if this solves your problem!

[echoari77]

Hi 👋

Thanks so much for the quick and detailed response — that was exactly what I needed!

I ran the SQL query you provided, and as expected, the CLIENT_STATUS for adminConsole was set to 2.
After updating it to 1, I was able to log into the Admin Console successfully.

Really appreciate your support and clear explanation. This helped resolve the issue quickly!