Incorrect protocol url and scope prefix used for MSOffice365Protocol
See original GitHub issueWhen using MSOffice365Protocol as the protocol, during authentication it always fails with error
Unable to fetch auth token. Error: (invalid_client) AADSTS700025: Client is public so neither 'client_assertion' nor 'client_secret' should be presented.
The issue was found to be the following
class MSOffice365Protocol(Protocol):
_protocol_url = 'https://outlook.office.com/api/'
_oauth_scope_prefix = 'https://outlook.office.com/'
After changing it to the following, it seems to work fine
_protocol_url = 'https://outlook.office365.com/api/'
_oauth_scope_prefix = 'https://outlook.office365.com/'
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Connection — O365 documentation - GitHub Pages
Initializes the oauth authorization flow, getting the authorization url that the user must approve. Parameters. requested_scopes (list[str]) – list of scopes to ...
Read more >O365 - PyPI
This project aims to make interacting with Microsoft Graph and Office 365 easy to do in a Pythonic way. Access to Email, Calendar,...
Read more >Hướng dẫn python-o365 - Hàng Hiệu
scopes = ['my_required_scopes'] # you can use scope helpers here (see Permissions and Scopes section) account = Account(credentials) if not account.
Read more >Untitled
The next step is to determine how to use this command. ... MSGraphProtocol to use the Microsoft Graph API; MSOffice365Protocol to use the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, I’ve further studied this issue.
You have to set the redirect uri. It’s not enough to check the checkbox for the redirect uri. You have to set the redirect uri text box with the desired redirect uri.
In the following image you can see that the textbox redirect uri is not set.
See #317
@rayeeskm can you check that? @Narcolapser is this your case?
On the contrary if you have set a public client on purpose… well this library is not yet prepared to handle a device authentication flow.
Closing this as there’s no answer from the user