Error listing oauth scopes (Unable to login for Achievement Example Scene) #328
-
Hi, When trying to login in the Achievement Example, using Dev Auth, I get the Error message [Error listing oauth scopes]. When using "Account Portal", the browser shows a message saying "Invalid Client" and "Client scopes are not configured". I have not found any reference to this, and my only guess would be a missing client in the developer portal, or a missing policy for that client. However, neither should be the case. Sorry if this is a beginner question, because it does feel like it would just be a missing part of the configuration either in the plugin or in the Epic project. But while I have been able to find and eventually solve the errors that came bevor, this time I am at a loss. Here are the logs as well.
Upon trying to login with Dev Auth:
Upon trying to login with Account Portal:
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Hi, were you running with a clone of the repo? or the UPM package of the plugin? |
Beta Was this translation helpful? Give feedback.
-
I was using the UPM package, imported from the newest tarball. After your question, I also tried to import it into Unity via the git link, with the same results. Configuration is all set as far as I can tell, but to make sure I'm not missing anything, here are the values I filled out: Product Name: Product Version: Product ID, Sandbox ID, Deployment ID, Client ID, Client Secret: Encryption Key: |
Beta Was this translation helpful? Give feedback.
-
I believe the issue is that the client scopes and the client on Epic's developer portal haven't been configured, so the plugin can't function. Have you configured a client yet on their back end? It will be under The title's page -> Product Settings -> Clients. |
Beta Was this translation helpful? Give feedback.
-
I have created a client, and linked it to a client policy. The policy uses the standard settings for achievements. If I understand it correctly, I should not have gotten a "Client ID" and "Client Secret" otherwise. I also believe that the client is correctly linked up with the rest of the product, since I can generate a header file in the main Product Settings, which includes that data together with everything else. However, I have not seen the the word "scopes" in any of these settings, or in the documentation. Only in the error messages and in your comment. Is there another place that these would need to be configured? |
Beta Was this translation helpful? Give feedback.
-
Alright, that got me on the right track, which was "search the general documentation for 'scopes' again and try out everything you find". For future reference, if anybody else has the same problem: Even if you want to use the standard settings, you have to "save" these settings once. That's what I did not do the last time, because no changes were needed. Thank you, to both of you! |
Beta Was this translation helpful? Give feedback.
Alright, that got me on the right track, which was "search the general documentation for 'scopes' again and try out everything you find".
For future reference, if anybody else has the same problem:
Epic Account Services -> Permissions -> Save Changes
Even if you want to use the standard settings, you have to "save" these settings once. That's what I did not do the last time, because no changes were needed.
Thank you, to both of you!