mattrogowski
Well-known member
Looks like whatever library you’re using is requesting a scope that doesn’t exist, this isn’t an OpenID implementation so there is no openid scope.
[TH] OAuth Integration [Deleted]
- Thread starter ThemeHouse
- Start date
Sprisa
Active member
What implementation is it then?
mattrogowski
Well-known member
It’s just standard OAuth.
Sprisa
Active member
I gotta contact auth.js then
W35K3R
Member
To resolve this issue, you can take one of the following approaches:
- Hardcode the scopes in the params object like this:
-
JavaScript:
authorization: { url: "https://<your_xf_forum_domain>/audapi/oauth2/authorize", params: { scope: "user:read thread:read etc:etc" }}
-
- Allow NextAuth to use all the scopes enabled in your OAuth2 Client setup for this addon during the authorization process by leaving the scopes property in the params object as an empty string:
-
JavaScript:
authorization: { url: "https://<your_xf_forum_domain>/audapi/oauth2/authorize", params: { scope: "" }}
-
Last edited:
Sprisa
Active member
Just got back to this old project. Can't go past it. Hopefully the native OAuth api will fix it
mattrogowski
Well-known member
Not sure what you mean, are you referring to the ability to use XenForo as an OAuth server in 2.3? From what's been covered about that you'll still need to send scopes. Either way, the issues you had here were entirely due to the client library you're using, so you'll likely continue having the same issues.
mattrogowski
Well-known member
What step is throwing the 401? I'm not sure what else you would like us to document as OAuth is an open standard so every implementation works the same way by definition. Aside from the endpoint URLs, there's nothing specific for us to document that's unique to this addon.
Sprisa
Active member
Callback is throwing 401
mattrogowski
Well-known member
Is there a specific error message as well as the status code? There should be a message explaining the error too.
mattrogowski
Well-known member
/api/me), you need to pass through the XenForo API key header too. That would need to be implemented into the library as the API calls are all standard XenForo, this addon just gives you the OAuth token aspect.Actually that might not be the case - if you can clarify if there's a specific error message, that might make it clearer what the issue is.
Last edited:
mattrogowski
Well-known member
If it helps, check to make sure the client credentials are being sent in the Body, not the Header. For example the miniOrange OAuth Client WordPress plugin has this option:
If this is set to Header it doesn't work. See if your library has a similar option and make sure it's set to Body.
If this is set to Header it doesn't work. See if your library has a similar option and make sure it's set to Body.
Jake B.
Well-known member
What "callback"? Is there a specific XF endpoint you're using? There should be an error message to go with it. Not really much we can provide if we're given no details on the issue, sadly.
Best guess would be if you're using Apache it will sometimes eat the Authorization header in certain configurations, there is a line in the default XenForo .htaccess file that you can uncomment to resolve this, nothing to do with this add-on, just a server configuration problem.
The line you can try to uncomment is below:
Code:
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]Sprisa
Active member
I'm using nginx, and it didn't return anything other than 401 Unauthorized
mattrogowski
Well-known member
It should definitely be returning a message string in the response body too, log out the full response and it should be there. Also check my previous post about how your library is sending the credentials to get the token. Ultimately there's not a lot we can do if we have no idea what the client library you're using is doing and how it's formatting the requests, or what the error message received is.
Sprisa
Active member
Do you know of any other libraries?
mattrogowski
Well-known member
Not specifically for javascript, but I Googled "javascript oauth client" and there's several options here: https://oauth.net/code/javascript/
It's probably not necessary to use a new library though if you can establish at least what the response error message is.
It's probably not necessary to use a new library though if you can establish at least what the response error message is.
W35K3R
Member
@Sprisa, my developer buddy figured out how to make this work with NextAuth. I'll generalize the custom provider code he created, and I'll get back to you on this as soon as I can. In the meantime, and if you haven't already done so, can you post what you have set up for the XenForo OAuth2 provider in regards to this add-on for your project? @mattrogowski, the add-on is not the issue; rather, there's a peculiar workflow implementation with NextAuth that has to be done a certain way to get the two to work together. You'd think they'd make this easy to integrate with custom OAuth2 providers lol, but it's never that easy, unfortunately 
Last edited:
Sprisa
Active member
Oh great! Is it still working?@Sprisa, my developer buddy figured out how to make this work with NextAuth. I'll generalize the custom provider code he created, and I'll get back to you on this as soon as I can. In the meantime, and if you haven't already done so, can you post what you have set up for the XenForo OAuth2 provider in regards to this add-on for your project? @mattrogowski, the add-on is not the issue; rather, there's a peculiar workflow implementation with NextAuth that has to be done a certain way to get the two to work together. You'd think they'd make this easy to integrate with custom OAuth2 providers lol, but it's never that easy, unfortunately