-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can no longer Authenticate #28
Comments
Is this project still maintained? At the very least is there someone around to verify this isnt an issue with my accounts? The issue exists within the Xbox Authentication Service Users (XASU). The 403 response is useless and does not really contain any information on what the problem is otherwise i would (attemp to) fix it myself. Thanks |
No it is not maintained anymore |
Try to prefix |
Hi, Thank you for your suggestion. Unfortunately this just results in a 400 Bad Request. Your help is much appreciated however. Thank You |
Hi, An update to this - I have figured out where the problem lies. The problem seems to be with the Access Token that is retrieved and is causing the XASURequest to fail with a 403. Line - [AccessToken = new AccessToken(windowsLiveTokens);] in [AuthenticateAsync()] in [AuthenticationService,cs]. I know this because I have injected a known working Access Token into the XASURequest and everything works correctly. Any thoughts? Thanks |
@tuxuser Found the problem. Client ID "0000000048093EE3" no longer appears to work. Changing this to a known working Client ID Fixes the issue. Thanks |
Nice you figured it out and thx for reporting back. I will keep this issue open for others to see. |
Hi,
Seems to be getting 403 Forbidden on attempts at Authentication, both Web & Headless. This appears to be a recent issue as this has only just stopped working recently. Tried with multiple accounts, same result.
Thanks
The text was updated successfully, but these errors were encountered: