Hello, we are since recently experiencing problems with our Android app accessing OneDrive via the following dependencies:
compile group: 'com.microsoft.services', name: 'odata-engine-core', version: '0.13.0'
compile group: 'com.microsoft.services', name: 'odata-engine-android-impl', version: '0.13.0', ext: 'aar'
compile group: 'com.microsoft.services', name: 'discovery-services', version: '0.13.0'
compile group: 'com.microsoft.aad', name: 'adal', version: '1.1.11'
compile group: 'com.microsoft.services', name: 'file-services', version: '0.11.1'
When we read the ServiceInfos returned by discoveryClient.getservices().read(); we now read a single service info which just has the Directory capability. Until some time ago what we used to obtain was at least one ServiceInfo which had a capability named MyFiles. We then checked for this specific capability and went on to our OneDrive using code without problems.
So now that we do not get this MyFiles cap, our application fails. If we try to test to skip this capability check in our own code and directly go to the OneDrive specific code, we then get 403 errors reported via Exception from your API.
The "Delegated Permissions" we are using in our application, set in the Azure Portal are:
Windows Azure Active Directory: (2 perms)
- Access the directory as the signed-in user
- Sign in and read user profile
Microsoft Graph: (5 perms)
- Have full access to user files
- Read user files
- Read items in all site collections
- Read files that the user selects
- Sign in and read user profile
Has anything changed? Do we need to delegate any additional permissions?
Or, maybe, should we now implement a different approach for any reason?
For the record, our iOS team using these deps for months now are experiencing no issues:
pod 'LiveSDK'
pod 'ADALiOS', '~> 1.2.2' # 1.2.2 < ver < 1.2.2
pod 'OrcEngine/Implementation', :git => 'https://github.com/MSOpenTech/orc-for-ios.git', :branch => 'dev'
pod 'Office365/Files', :git => 'https://github.com/greathansen/Office-365-SDK-for-iOS', :branch => 'orc-poc'`
Thanks in advance!
Hello, we are since recently experiencing problems with our Android app accessing OneDrive via the following dependencies:
When we read the
ServiceInfos returned bydiscoveryClient.getservices().read();we now read a single service info which just has theDirectorycapability. Until some time ago what we used to obtain was at least oneServiceInfowhich had a capability namedMyFiles. We then checked for this specific capability and went on to our OneDrive using code without problems.So now that we do not get this
MyFilescap, our application fails. If we try to test to skip this capability check in our own code and directly go to the OneDrive specific code, we then get 403 errors reported via Exception from your API.The "Delegated Permissions" we are using in our application, set in the Azure Portal are:
Windows Azure Active Directory: (2 perms)
Microsoft Graph: (5 perms)
Has anything changed? Do we need to delegate any additional permissions?
Or, maybe, should we now implement a different approach for any reason?
For the record, our iOS team using these deps for months now are experiencing no issues:
Thanks in advance!