Hi Michael, The short version is: most clients don't natively do OAuth. You're stuck to using Basic or Digest auth. What this can mean in practice is, that the user needs to authenticate externally from sabredav with the remote service, and then your application would have to generate a username + password pair that 'represents' their OAuth credentials. For a sane user-experience, the credentials can't really expire either, adding to the frustration =)
That's how we do it when integrating with OAuth or SSO systems. Evert On Thursday, November 6, 2014 8:45:27 AM UTC-3, mbiebl wrote: > > Hi, > > I have a setup, where users are defined in a Azure AD and I want to make > SabreDAV authenticate those users against Azure AD. > With OpenLDAP or Active Directory, authentication is pretty simple. I use > HTTP basic and the clients provide a username and password, which are then > used in validateUserPass() to make a bind against the directory server. > This works nicely with all clients I tested so far. > > I'm a newbie when it comes to Azure AD, but from what I read so far, I > can't do something like a simple bind against a Azure AD and I'll have to > use a mechanism like OAuth 2.0. > Has anyone experience with CardDAV and OAuth 2.0 in general and SabreDAV > and Azure AD in particular? > I'm a bit lost at how to implement that on the SabreDAV side and what that > means for the client, .say I have a mobile device like an iPhone, which I > want to use to access the SabreDAV CardDAV Server. > > I'm grateful for any pointers. > > Michael > > > -- You received this message because you are subscribed to the Google Groups "SabreDAV Discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sabredav-discuss/7d0c61c3-4ec7-456c-afde-93374fb9b515%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
