woloski

Senior Software Engineers

Remote required

Auth0 is a privately-held tech company based in Seattle, WA. We have a distributed team working remotely from Seattle, Buenos Aires and Cordoba.

• We are building our product on top of nodejs, mongodb, linux, puppet among other technologies. Our infrastructure process thousands of logins a day.
• We believe in Open Source, we enjoy sharing what we've learnt
• We are bootstrapped, profitable, & proud to be ending our first year in business with happy, paying customers!

We're building the company we always wanted, with people who share the same passion for technology, solutions and customers.

woloski

'use latest';

import express from 'express';
import { fromExpress } from 'webtask-tools';
import bodyParser from 'body-parser';
const app = express();

var jwt = require('express-jwt');

var jwtCheck = jwt({

woloski

Introducing Webtask Editor

The Webtask Editor is a web based editor (and soon an Electron desktop app) to create and edit webtasks. This started as a side project but it quickly became clear that the editor would help adopt the serverless concept webtask Our goal is to reduce the time it takes to go from an idea => code => HTTPS endpoint.

The Power of WYSWYG

One of the tools many of us enjoyed using a lot in the old days was the SQL Explorer. The instant feedback you've got when executing queries was great. Edit your query, CTRL+R, see the result, teak the query, CTRL+R, and repeat that loop until you got it right.

woloski

wt create webtask.js --auth0

When browsing the webtask URL, the user will get a page with Lock. Once logged in, the result of the webtask will be shown.

woloski

This is preliminary feature to add rules into the Client Credentials exchange pipeline (i.e. exchange a client_id and secret for an access_token).

To create a rule that runs on the client credentials exchange you have to use the webtask CLI (wt). To install the CLI, you can follow the steps here: https://manage.auth0.com/#/account/webtasks.

Assuming you have an API defined with scopes (https://manage.auth0.com/#/apis) and you created a non-interactive client (https://manage.auth0.com/#/applications) and authorized it to use that API, follow these steps to create a rule.

Currenlt you can create only one rule that will be executed for all clients and APIs.

1. The first step is to create the webtask rule. Create a file myrule.js and enter the following. This is an example rule that will add an arbitrary claim (https://foo.com/claim) to the access_token and will also add an extra scope to the default scopes configured on the API (https://

woloski

Public Functions

I will create a hello world function:

echo "module.exports = function(ctx, cb) { cb(null, 'hello'); }" > hello.js
wt create hello.js

woloski

/* ------------------ GENERAL --------------- */

/* change default fonts  */
@import url(https://fonts.googleapis.com/css?family=Open+Sans:700,800,400);
.popup {
  font-family: 'Open Sans', sans-serif;
}

/* login widget width and centered position  */
.popup .overlay .onestep {

woloski

1. Create a new Database Connection in Auth0 Dashboard
2. Give it an arbitrary name (myapp.com)
3. Delete the content and paste the content of the script
4. Replace the BASE_URL with yours
5. Click on Try button and check if it works
6. You can now use the Login Widget through https://YOUR_SUBDOMAIN.auth0.com/login?client=YOUR_CLIENT_ID (both values can be found on Settings)

woloski

using System.Linq;
using System.Threading;
using Microsoft.IdentityModel.Claims;
using ServiceStack.Common.Web;
using ServiceStack.Configuration;
using ServiceStack.ServiceInterface;
using ServiceStack.ServiceInterface.Auth;

namespace YourApp
{

woloski

PS C:\> Enable-Auth0 -auth0Domain:"foo.auth0.com" -clientId:"Jr22cCJ3C....b6AXQKws" -webAppUrl:"http://sp2010app:8002" -identifierClaimType:"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" -claims:@("Email|http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress") -Verbose

VERBOSE: Adding Microsoft.Sharepoint.Powershell Snapin
VERBOSE: Leaving BeginProcessing Method of Get-SPShellAdmin.
VERBOSE: Leaving ProcessRecord Method of Get-SPShellAdmin.
VERBOSE: Leaving EndProcessing Method of Get-SPShellAdmin.
VERBOSE: Downloading federation metadata from
http://foo.woloski.auth0.com/wsfed/Jr22cCJ3C....b6AXQKws/FederationMetadata/2007-06/FederationMetadata.xml
VERBOSE: Check App exists
VERBOSE: Leaving BeginProcessing Method of Get-SPWebApplication.