Is it (or will it be) possible to log-in to 365 (or share content) with other OAuth supported mechanisms? e.g. could I share a document library with a LinkedIn or Facebook user? Is this on the plans?
There’s also some comments being spawned on my FB Discussion :
As an update to this post, Chris Givens has kindly shared his wisdom on this issue in his post here. I am sure Chris won’t mind me sharing this phrase key section :
“If you want to use something other than ADFS, well, you better dig in for doing a ton of research on how WS-Fed and WS-Trust works and similarly, OAuth. If you don’t have time for that, then you’ll need to request the services of people that do know that space. Unfortunately, having the identity management skills matched with an understanding of the future of App Models across vendors is a rare breed of consultant. You also have to contend with a cold hard fact:
- Currently, Office 365 only supports users of your verified domains (such as contoso.com)“.
If this is something you are thinking of doing (as we are at Collaboris), then I strongly urge you to take a look at Chris’s post.
Update – Chris Johnson shared some awesome information on Chris Givens FB discussion – so I am sharing it onwards :
It is possible to use different Identity Providers with Office 365 but they need to be approved by the 365 Team first. Here is a list of third party identity providers that are supported (and pasted here).
- Optimal IDM Virtual Identity Server Federation Services
- PingFederate® 6.11
- Centrify
- IBM Tivoli Federated Identity Manager 6.2.2
- SecureAuth IdP 7.2.0
- CA SiteMinder 12.52
- RadiantOne CFS 3.0
- Okta
- OneLogin
To get the run down on how you apply and qualify to be a 3rd part provider you need to read this and this.
cheers mate – I have updated the main discussion to include a link to your post. Thanks for taking the time to sift through this. Please keep me updated as you learn more, as this is definitely something I need and don’t want to get locked into an AD implementation.
Mark Wilson just pointed me in this direction :Â http://blogs.technet.com/b/meamcs/archive/2013/06/01/use-facebook-as-an-identity-provider-for-sharepoint-2013-part-1.aspx
It looks like you can organise contacts from other social networks :Â http://community.office365.com/en-us/b/office_365_community_blog/ar…, but I want to be able to share content or login.
However, Chris Givens has also written a post called ‘ACS is dead‘ which concludes that we should be using middleware solutions such as ‘Auth0’