Office 365 APIs, OAuth, Consent Flow

Leddura 2Share Pro/Kickle uses OpenID authentication to get access to Office 365 resources. Authentication principles are detailed here: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols.

These permissions are OAuth standard permissions (based on Azure AD Application specifications). Leddura 2Share Pro/Kickle needs to access your O365 Online instance to read the contact list, etc., as a normal user would do (same "level" permissions as a normal user). The "consent" is an activation in your O365 tenant, to specify that "2Share Pro/Kickle is an application and will need to authenticate to O365 with a user account".  

Note: To use these Office 365 APIs, it is necessary to use a O365 account which is authenticated on the specified Office 365 tenant, and to specify the application ID. CTOUCH and/or Kickle employees CANNOT access these APIs.

Consent link Leddura 2Share Pro (to be executed by O365 Tenant Administrator):

https://login.microsoftonline.com/common/adminconsent?client_id=e10e51fc-56d7-49d1-ad31-96ec3940a4b5&state=12345&redirect_uri=https://www.kickle.com

The authorization scope Leddura 2Share Pro