Hello.
There is a problem when issuing refresh_tokens after issuing it to User Credentials, how do I handle it? Your help would be greatly appreciated!
The problem is
When Grant_types is first issued in the oauth_clients table, if it is successfully issued in password,
When issuing a refresh_token, grant_types checks with a refresh_token value
{
"error": "unauthorized_client",
"error_description": "The grant type is unauthorized for this client_id"
}
An error occurs.
Forced to the database
INSERT INTO webbit.oauth_clients (client_id, client_secret, grant_types, scope) VALUES ('testclient2', 'testsecret', 'refresh_token', 'app');
I'll put in the data
In the oauth_refresh_tokens table,
If you force the client_id value of the root from db to testclient2 and call api, the token will be reissued normally.
Hello. There is a problem when issuing refresh_tokens after issuing it to User Credentials, how do I handle it? Your help would be greatly appreciated!
The problem is When Grant_types is first issued in the oauth_clients table, if it is successfully issued in password, When issuing a refresh_token, grant_types checks with a refresh_token value
{ "error": "unauthorized_client", "error_description": "The grant type is unauthorized for this client_id" }
An error occurs.
Forced to the database INSERT INTO
webbit
.oauth_clients
(client_id
,client_secret
,grant_types
,scope
) VALUES ('testclient2', 'testsecret', 'refresh_token', 'app'); I'll put in the data In the oauth_refresh_tokens table, If you force the client_id value of the root from db to testclient2 and call api, the token will be reissued normally.