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
Interoperability with Sharepoint on Office 365 #9103
Comments
Looks like a proprietary authentication model that we cannot currently support. |
I coulda told you that it was non-standard, certainly :) You might want to let your social media team know, they had informed me that it should work. I'd also like to lodge a feature request for this support. From what I understand there is a way to work with it now. I'm not sure about the details, but a couple other programs I've been experimenting with said that they were currently working on adding the feature in a future update. |
Unless you have setup Active Directory Federation Services (ADFS), Sharepoint Online exclusively needs Claims-Based Authentication based on WS-Federation which Cyberduck currently does not support. With ADFS configured you can authenticate through NTLM which Cyberduck supports. There is currently no Java library supporting Claims-Based Authentication against Sharepoint Online. A few resources that could help to implement it in Java:
|
We will provide support by integrating support for OneDrive.
|
When I try to connect to my company's Sharepoint hosted on Office 365, I get "403 FORBIDDEN". I had the IT manager check settings and try to fiddle with a few things as well, but nothing changed that error.
Searching online, it seems like there may be some terminal commands to show hidden options to get Sharepoint on Office 365 to work (since it's IWA), but it's not entirely clear.
I asked on Twitter whether Cyberduck is supposed to support Sharepoint like this and was told yes, and when I followed up with this issue, I was asked to submit a support ticket with the log drawer, which is below:
The text was updated successfully, but these errors were encountered: