Issue on Version 3.5.2

Hey @byronbehm … did you figure it out? Let me know if not, happy to help!

I’m having issues with this as well. I tried both of the options available, but I can’t get it to go away and work.

IMPORTANT!

WP-Auth0 has upgraded to 3.5.2 but could not complete the upgrade in your Auth0 dashboard.	This can be fixed one of 2 ways:

1. Create a new Management API token and save it in the Auth0 > Settings > Basic tab > API Token field.	This will run the update process again.

2. Review your Client advanced settings, specifically the Grant Types, and authorize your client for the Management API to manually complete the setup.

This banner will disappear once the process is complete.

I added all of the GRANTS to my Client from the new API that I created — they match what’s shown here: https://auth0.com/docs/cms/wordpress/configuration#authorize-the-client-for-the-management-api

What am I missing?

Sorry for the trouble @xzistance3. Are you having any issues with logins at all? If so, do you have “Implicit Mode” turned on under Auth0 > Settings > Advanced?

If you would, follow those API token steps again and check Auth0 > Error Log for anything relevant appearing there.

Also make sure to walk through the Client Setup section as well, it’s possible that Client Credentials is not active for the Client you’re using:

https://auth0.com/docs/cms/wordpress/configuration#client-setup

Thanks Josh.

Here are some of the errors I’m getting in the log:

03/08/2018 19:44:38	WP_Auth0_Api_Client::get_client_token	N/A	{"error":"access_denied","error_description":"Client is not authorized to access \"https://[TENANTID].auth0.com/api/v2/\". You might probably want to create a \"client-grant\" associated to this API. See: https://auth0.com/docs/api/v2#!/Client_Grants/post_client_grants"}

03/08/2018 19:44:33	WP_Auth0_Api_Client::get_client_token	N/A	{"error":"access_denied","error_description":"Client is not authorized to access \"https://[TENANTID].auth0.com/api/v2/\". You might probably want to create a \"client-grant\" associated to this API. See: https://auth0.com/docs/api/v2#!/Client_Grants/post_client_grants"}

03/08/2018 19:44:31	WP_Auth0_DBManager::install_db	N/A	Unable to automatically update Client Grant Type. Please go to your Auth0 Dashboard and add Client Credentials to your Client settings > Advanced > Grant Types for ID [CLIENTID]

03/08/2018 19:44:31	WP_Auth0_Api_Client::get_client	N/A	{"statusCode":401,"error":"Unauthorized","message":"Bad audience: [SITEURL]"}

03/08/2018 19:44:31	WP_Auth0_DBManager::install_db	N/A	Unable to automatically update Client Grant Type. Please go to your Auth0 Dashboard and add Client Credentials to your Client settings > Advanced > Grant Types for ID [CLIENTID]

03/08/2018 19:44:31	WP_Auth0_Api_Client::get_client	N/A	{"statusCode":401,"error":"Unauthorized","message":"Bad audience: [SITEURL]"}

03/08/2018 19:44:30	WP_Auth0_DBManager::install_db	N/A	Unable to automatically create Client Grant. Please go to your Auth0 Dashboard and authorize your Client [CLIENTID] for management API scopes update:clients, update:connections, create:connections, read:connections, create:rules, delete:rules, read:users, update:users, update:guardian_factors.

03/08/2018 19:44:30	WP_Auth0_Api_Client::update_client	N/A	{"statusCode":401,"error":"Unauthorized","message":"Bad audience: [SITEURL]"}

03/08/2018 19:44:30	WP_Auth0_Api_Client::update_client	N/A	{"statusCode":401,"error":"Unauthorized","message":"Bad audience: [SITEURL]"}

• This reply was modified 6 years, 8 months ago by xzistance3.

FYI, I submitted a help ticket on support.auth0.com — If you’re able to utilize that system, we can exchange more detailed info. Request # is 36989

I double checked the 2 Client Grant errors and the Client should have those grants enabled.

I’ll continue there. Thanks!

Hi Josh,

I was not able to see the conclusion of this issue–we are having the same problem. We have reverted to 3.2.13. But are getting warnings about expiring endpoints.

Were you able to help xzistance3?

Steve

@stevejohanson – yes, we narrowed it down to one of the following:

– the Client Grant in Client Settings > Advanced > Grant Types is turned off (dashboard)
– the Client needs to be authorized at APIs > Auth0 Management API > Clients (dashboard)
– the Audience field was changed in wp-admin > Auth0 > Settings > Basic > Audience (should be “https://your-tenant.auth0.com/api/v2”)

Let me know if that doesn’t help!

Thanks Josh,

We have already been over the first to bullet points and they check out. The third…can I ask a lazy question–is that a field that shows up in 3.5.2? Because I do not see it in Auth0 > Settings > Basic for 3.2.13.

Steve

Yes you can and yes it does ??

Hi Josh,

I verified all three of these items you listed above:

– the Client Grant in Client Settings > Advanced > Grant Types is turned off (dashboard)
– the Client needs to be authorized at APIs > Auth0 Management API > Clients (dashboard)
– the Audience field was changed in wp-admin > Auth0 > Settings > Basic > Audience (should be “https://your-tenant.auth0.com/api/v2”)

But I am still getting an error. Here are the columns from the Plug in error log:

-04/18/2018 18:07:54
-WP_Auth0_LoginManager::redirect_login => $this->login_user()
-invalid_grant
-Invalid authorization code

This obviously implies that I have not added the correct grants to Auth0, but I used the ones in the setup page:

create:clients
update:clients
update:connections
create:connections
read:connections
create:rules
delete:rules
read:users
update:users
create:users
update:guardian_factors

And ideas about this?

Steve

the Client Grant in Client Settings > Advanced > Grant Types is turned off

Hmm … I’m not sure what you’re saying here. Under the Application > Advanced > Grant Types you want Authorization Code and Client Credentials, at least:

Are you seeing an error message in the browser when you try to login? Looking at the code, it looks like it might be an issue with your Client Secret. Try copy-pasting that in again from your Application settings and check to make sure the JWT Signing Algorithms match (either HS256 or RS256, should be the same in the dashboard and in wp-admin).

Also, make sure your audience has a trailing slash on there, it’s an ID (I realize now I got that wrong, apologies if that was the issue).

The colon-separated values you pasted there are scopes for the management API. Grants are more like a “type” of access.

• This reply was modified 6 years, 7 months ago by Josh C.

Josh, Thank you for your patience. It was the signing algorithm HS256 vs. RS256. A rookie mistake. But for some reason they changed when I did the upgrade.

But it is a good checklist item for your troubleshooting guide.

Steve

Good to hear, Steve, thanks for checking back in. I have it on my list to update the troubleshooting guide with this.