Last week we added support to Auth0 to integrate with Salesforce.com. This means that you can now enjoy SSO with Salesforce with any of our supported Identity Providers in minutes.
How does it work?
Salesforce implements the SAML Protocol for authentication and identity federation. Auth0 bridges SAML-P with whatever your preferred Identity Provider implements: SAML, OAuth 1, OAuth 2, LDAP, a SQL database, anything.Read more...
When you "claims enable" SharePoint with Auth0, you also get an enhanced People Picker. This is optional, because it doesn't intervene in then authentication process, but is a very handy feature that prevents common mistakes, errors, and a superior user experience.
If you enable the Auth0 People Picker you will be able to resolve names and search contacts across all configured identity providers.
Startup in-a-Box Bootcamp
This is an event that happened simultanesouly around the globe in 93 cities!
Our theme for the event was: "Startup in-a-box". We wanted to share with the community what we have been using to get our Startup going: our tools, frameworks, and processes that we use daily in our company.
These are some numbers for the day:
- 40 showed up on Saturday. That's a pretty good turn up of all registered users. Clearly, there's interest, thanks everyone!
- Everyone stayed till 6pm (that is 9 hours of training on a Saturday!)
- Very high level of satisfaction: 90% of the attendees rated the event gave at the highest score.
- 6 presentations and Hands on Labs, covering node.js, mongodb, Windows Azure, Auth0, GitHub and Jenkins
- 8 organizers (most of them working on startups) to make sure everyone could get their questions answered:
We have good news for our colleagues developing on Ruby. Last week we relased the Auth0 OmniAuth Strategy that makes it a bliss to connect Ruby apps with Auth0.
OmniAuth is a Ruby authentication framework aimed to abstract away the difficulties of working with various types of authentication providers. It is meant to be hooked up to just about any system, from social networks to enterprise systems to simple username and password authentication.
Once you connect to Auth0, you can automagically accept users from anywhere: LDAP, AD, SQL, Office365, Google Apps, LiveID, Facebook, Twitter, PayPal, LinkedIn, etc.Read more...
Many companies rely on databases to store user credentials. Either because they use pre-built systems like ASP.NET Membership, or because they wanted to keep those users outside their main identity system (e.g. Active Directory) or just because of historical reasons ... (a.k.a. legacy)
In fact, one of the most requested features in ADFS was the ability to authenticate users outside AD. A very annoying limitation in the product, that still has not been addressed.
Because this is so common, we decided to support it out of the box in Auth0. The Auth0 Custom Connector is a component that you deploy to your infrastructure, that connects to any database (or anything really), and seamlessly integrates with Auth0.
Once setup is done (a very simple process in itself), you can continue to leverage those identities and connect them with any apps supported by Auth0: SharePoint, CRM, mobile, etc.
Here's the entire process in less than 3 minutes:Read more...
This week Microsoft announced the general availability of Windows Azure Active Directory (read ScottGu, Vittorio and Alex for the official word). We are very happy to see this milestone happening. We've been privileged to have been working with their team for quite some time now, and we think it is great news for the identity community. Congrats again on the release! This opens lots of opportunities for developers.
Why we think Windows Azure AD is important
Every app that creates a new user database contributes to Global Warming, and kills millions of kittens :-) -- the internet
This last release of Azure AD contributes greatly to the adoption of more modern identity architectures. Hundreds of thousands of companies rely on Active Directory today. Azure AD brings you closer to the (not anymore) utopia of connnecting organizations seamlessly and securely.
But what exactly is Azure AD? It is not a Domain Controller in the cloud. It is more like a combination of AD and ADFS with a more modern API to query the directory. It runs on the cloud and it can run as a the primary user directory for an organization or synced against an on-premise AD and federated with ADFS (it won't save passwords in the cloud). Even more enticing is the fact that it is free!
How does Auth0 work with Azure AD?
On our side, we've just completed the integration of Windows Azure AD in Auth0, and it is already enabled for our customers.
This means you can integrate your app with a single standard API and you will now enjoy easy access to Windows Azure AD and the rest of the identities we support: Google Apps, on-premises Active Directory with and without ADFS, user accounts stored in SQL databases, Facebook, GitHub, LinkedIn, Twitter, PayPal, etc.
In summary, with Auth0 you get:Read more...
If your app uses Auth0 for authenticating users, adding SSO with LinkedIn, PayPal, GitHub, Twitter and Facebook is just a click away:
Each provider configuration page will allow you to fine tune the information you'd like your customers to disclose. As an example, when selecting PayPal you can choose to request:Read more...
Supporting SharePoint is a prime scenario in Auth0 and it's fully integrated into it. In this post we show how SharePoint can accept users authenticated in Google and Office365. In this other one we do the same with a partner using Active Directory.
In this post, we show how easy it is to configure SharePoint for claims based authentication.Read more...
WAMS already ships with support for single-sign-on with social identity providers (e.g Facebook, LiveID), but no support for enterprise providers: Google Apps, Office 365 and Active Directory; or even custom SQL user databases. Even for social providers, it currently doesn't allow finer grain control on what information the user has to consent to disclose.Read more...
Here's another scenario supported by Auth0 out of the box, with no special configuration.
Contoso is a company that does business with many external people, and they need to share Word and Excel documents with them in a secure way.
They need to specify and enforce specific rights on these documents:
- Can you print?
- Can you edit?
- Can you forward it to someone else?
AD Rights Mangament Services (RMS) is a great technology to do exactly that, but not surprisingly, it is optimized to be used with Active Directory.
With Auth0, you can now extend RMS to users outside your domain, and continue to benefit from these access policies:
Auth0 is about making identity simple. And even simpler for the most common and recurrent scenarios.
One such scenario is a company that is using SharePoint on-premises and has moved e-mail to Office365. They might not yet be ready for using SharePoint in the cloud (e.g. don't have the time for a migration to the cloud, or need more advanced customization than what Office365 offers).
Auth0 supports many common identity scenarios. One of them is a SaaS app being used by companies with their own identity systems. This is the classic federation scenario.
To illustrate this, lets start by introducing the characters:
- Fabrikom is a small business, using Office365
- MDOCS is a document sharing app hosted in the cloud