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
consumer_key consumer_secret for Windows Live Oauth2 #187
Comments
It look like Microsoft has completely revamped its Oauth2 login. Authomatic seems to support v1 and the latest is v2. It looks like v1 credentials still work but if you create new credentials, they will be v2 credentials what won't work with Authomatic. To answer my previous question, the ttf*** is the right secret key to use. I'm working on creating a new WindowsLiveV2 Oauth2 class but it is slow going because Oauth2 details are all new to me. The code below is getting me part of the way there and I'll keep working on it.
|
I'm getting close with this code:
I get this error:
I'm using this for the scope: I expect that I need to do something different in |
Sorry the serial posts about this. I kept thinking I was going to stop but I kept working on it, and now I have something working. Here is some code with comments:
See the comment in the docstring regarding the scopes to use with this. I'm not sure if you need to further validate the user info received in |
Thanks for the work! Do you think you can provide a Pull-Request with a fixed provider? |
Sure, I've never done a pull request so give me some time to figure that out. Do you know if the existing Windows Live provider still works? If so, we should this as an additional provider instead of replacing the existing one. |
Here is an update to the above code so that it works with Microsoft business accounts. For some bizarre reason, Microsoft returns different info depending on whether it is a business or personal account.
|
After several years of inactivity, We are now reviewing all issues and PRs and hoping to begin work to solve as many of these as possible. We are keen to find out which issues still apply, and which PRs are still required/are likely to merge cleanly into the current code. We are aiming to review them all, but any help with prioritisation would be very useful! If you are still interested in having this issue/PR resolved, or are able to help us work on it, please reply to this message. That way we know which issues are most important to the community. |
I'm trying to setup Windows Live Oauth2, but I'm having trouble knowing what to use for the
consumer_key
and theconsumer_secret
. Below is a screen shot from this site: https://apps.dev.microsoft.com/?mkt=en-us#/appListFor
consumer_key
, I'm using the "Application Id" in the screenshot. Forconsumer_secret
, I've tried:In all cases, I get the error: "The client does not have a secret configured." Any help would be appreciated.
The text was updated successfully, but these errors were encountered: