woloski

Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client-organizations (tenants)

Let's start by enumerating some multi tenant applications and understand how they handle it.

Slack

Authentication:

woloski

function (user, context, callback) {
  // 
  // this rule can be used if you have chosen to use Username as the way to identify a user in Salesforce. Notice that we are mapping the email to the nameidentifier.
  //
  if (context.clientName === 'Salesforce') { 
    context.samlConfiguration.mappings = {
      'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier': 'email',
      'User.Username': 'email',
      'User.Email':   'email',
      'User.FirstName': 'given_name',

woloski

const emailVerifier = require("verifier-node");
module.exports = function (user, context, cb) {
  var response = {};

  emailVerifier.verify(user.email,  context.webtask.secrets.VERIFIER_APIKEY)
  .then(response => {
    
    if (!response.valid()) return cb(new Error('Disposable email!'));

    response.user = user;    

woloski

Hey {user || there},

For the last few months, we've been working on many new features and improvements to the platform. We thought it was a good time to re-connect and give you a quick update about Auth0.

We have reached 1300+ subscribers to our service, and there are many companies using the private cloud/on-premises appliance daily. Thanks for your support, feedback and business!

Here are some of the things we thought you might find useful:

1. Know who is using your apps
2. Richer user profiles

woloski

This would be the console output

Claims for: https://myadfs/ (Correlation: 84b46102-3ed2-4ff2-88ac-eace0709667c)
        http://schemas.microsoft.com/ws/2008/06/identity/claims/organization : myadfs
        http://schemas.microsoft.com/ws/2008/06/identity/claims/authenticationinstant : 2012-04-12T21:15:32.410Z
        http://schemas.microsoft.com/ws/2008/06/identity/claims/authenticationmethod : http://schemas.microsoft.com/ws/20
enticationmethod/windows
        http://schemas.microsoft.com/ws/2008/06/identity/claims/primarygroupsid : S-1-5-21-1409732942-2814574796-20323036
        http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid : S-1-5-21-1409732942-2814574796-203230364-513
        http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid : S-1-1-0

woloski

<button class="pay">Pay</button>

<script src="https://checkout.stripe.com/checkout.js">
<script>
    var handler = StripeCheckout.configure({
      key: window.STRIPE_PUBLICK_KEY,
      image: 'https://yourlogo.png',
      locale: 'auto',
      token: function(token) {
        $('.pay').prop("disabled", true);

woloski

1. Install the Custom Social Connections extension
2. Click on the Slack button to install the Slack connection
3. Enter a Slack Client ID and Secret. To get those go to: https://api.slack.com/apps/new. Fill the fields and pay special attention to the Redirect URI. Enter: https://YOURS.auth0.com/login/callback. See screenshots below.
4. Click on App Credentials on the left and copy the Client ID and Client Secret and paste them on the Auth0 dashboard
5. Click Save and then try the flow using the Try button. You should get back the full profile from Slack, including email, team and avatars.

Note: you can change the scopes on the Scope field on Auth0 and include any of these: https://api.slack.com/docs/oauth-scopes

You can now use the Slack connection using any Auth0 client library. Example:

woloski

• bcrypt: A bcrypt library for NodeJS.
• pg: PostgreSQL client - pure javascript & libpq with the same API
• q: A library for promises (CommonJS/Promises/A,B,D)
• node-uuid: Rigorous implementation of RFC4122 (v1 and v4) UUIDs.
• optimist: Light-weight option parsing with an argv hash. No optstrings attached.
• aws-sdk: AWS SDK for JavaScript
• validator: String validation and sanitization
• cheerio: Tiny, fast, and elegant implementation of core jQuery designed specifically for the server
• knox: Amazon S3 client
• consolidate: Template engine consolidation library

woloski

import webapp2
import urllib2
import urllib
import json

## CHANGE THIS
CLIENT_ID = "vYPeq7LGf1utg2dbDlGKCwGKgy94lPH0"
CLIENT_SECRET = "DLQ5dWkNMwPlUWo2jqVkbG1PFyeMvV60HEJaW0FioeI4ZxGaAW73BiqRBZmRk29v"
DOMAIN = "contoso.auth0.com"
CALLBACK_URL = "http://localhost:8080/callback"

woloski

1. Create a Client ID and an API Key on Google API Console. Set the Allowed Origins (e.g. localhost:3000).
2. Create an app in Auth0 and set the Allowed Origins (e.g. localhost:3000) and the callback to https://yours.auth0.com/mobile