-
Notifications
You must be signed in to change notification settings - Fork 8
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
error with scripts.generate_token: AttributeError: 'Connection' object has no attribute 'check_token_file' #1
Comments
Hi @adieball, we are currently using the version 1.1.3 of the O365 library and have not updated to version 2.x (yet). For the time being it might help to install O365==1.1.3 with pip and rerun the generate_token script. But be aware that you have to change the redirect URLs in the URL with is printed by the script. |
@lusiux that works much better, thanks. I have created a resource in O365 Exchange admin, i.e. the meeting room. That one now has a "user" with the email and a password. Now I can the generate_token script, which gives me the following url to call:
which part do I need to change now? V2.0 to V1.0? That doesn't work and just downloads an empty authorise.dms file. If I just call the URL as given, I get asked to login. Doing so using the meetingroomuser email and password, which immediately after that is asking me again to login for owa. I use the same username / password and I'm in OWA for that meeting room user, but nowhere in the process I had to give consent to any application. The URL I was given just before the second login (the one to OWA) looks like:
But if I copy that into the cli, I get:
|
The part of the URL which has to be changed is the The redirect URL has to be enabled in Exchange admin. |
Hi @lusiux much better but still not there :-) Now I get (after giving consent): AADSTS50011: The reply url specified in the request does not match the reply urls configured for the application: 'AAAABBBBBBCCCCCC'.` the URL actually has "outlook.office365.com/owa in there, although I changed the redirect URL to https://login.microsoftonline.com/common/oauth2/nativeclient (see manifest further down) You also said, the new redirect URL has to be enabled in Exchange Admin. Any tips where? I can't find anything like that. Seems since you build the logic, a lot has changed (Azure, app registration options, python module, etc) maybe time to create a new version? happy to assist wherever I can Maybe it helps to see the manifest: |
I am having the exact same issue too. If i can assist with logs or error messages please let me know |
We will have to switch to the new O365 authentication method sooner or later anyways (as the current system will shut down soon). Once that happens we will definitely update this repository. Not sure when we'll have the time to do it though. |
Is there any current news here? Unable to fetch auth token. Error: (missing_code) Missing code parameter in response. |
I've just brought this repository up to date with our internal development state. This includes a bunch of commits to migrate the authentication backend to the new O365 method. This should hopefully fix the issue. |
Now I was able to generate the o365_token.txt For one or the other perhaps still a help. In the Azure AD app, I have stored these three addresses as redirect addresses, and only then did it return the required token: https://outlook.office365.com/owa/ |
Probably a stupid question, but how does it go on now that I get the display to run :) |
When you create an appointment in the Outlook calendar associated with the display, you can watch it pop up on the display when its time has come. If |
Ok thanks, but that's not my real problem. I can't get the app to start. It's probably just me and my knowledge of Kivy. I have successfully gone through all the points from the description, now it's just a matter of how I get the app to run with Kivy. Maybe there is a HowTo for this? |
Are you getting any concrete error messages or backtraces? |
Hi
when executing python3 -m scripts.generate_token, I'll get the following error:
/cut/
/cut/
any helping hands / ideas on that?
The text was updated successfully, but these errors were encountered: