Sign inDemoInstall


Package Overview
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies



Version published



Build Status License


An Openwhisk action that uses PassportJS for User Authentication Proxy.

The scope of this action is to authenticate users, returning an Access Token, a Refresh Token, and the Profile of the user. The output of this action should be cached, encrypted with Openwhisk's namespace credentials or other means; actions belonging to the same package should be able to access this cache, retrieve a valid token, in order to be able to execute actions on behalf of the users.


Quick start

  1. Run npm install

  2. Create a webaction for an authentication provider.

    # (optional) place the action in a package
    $ wsk package create oauth
    $ wsk action create oauth/<action_name> ./openwhisk-passport-auth-0.0.1.js  --web true \
        --param auth_provider <authentication_provider> \
        --param client_id <client_id> \
        --param client_secret <client_secret> \
        --param scopes <comma_sepparated_scopes> \
        --param callback_url https://<openwhisk_hostname>/api/v1/web/<openwhisk_namespace>/oauth/<action_name>.json

    Configure the default action parameters:

    • auth_provider - the name of the authentication provider ( i.e. facebook, github, etc ). The action will try importing passport-<provider> lib. You can also add your own authentication provider.
    • auth_provider_name - optional; defaults to auth_provider; it defines an alternate name for the authorization to be used with Passport.
    • client_id - consumer key
    • client_secret - consumer secret
    • scopes - optional; the list of scopes to request
    • callback_url - this parameter should point to this action
    • success_redirect - a URL to redirect after a successful login. This value is cached in a cookie named __Secure-auth_context in order to be retrieved when the authentication provider invokes the callback_url.
  3. To test the action browse to https://<openwhisk_hostname>/api/v1/web/<openwhisk_namespace>/oauth/<action_name>

Using the built-in OAuth providers

The examples bellow assume there is a local OpenWhisk deployment, accessible on localhost, and an oauth package already created in OpenWhisk.

$ wsk package create oauth

Visit to create a new application, or to retrieve the Client ID and Client Secret for an existing application.

NOTE: When configuring the application in GitHub make sure the Authorization callback URL is set to https://localhost/api/v1/web/guest/oauth/github.json

Create a new action called github inside the oauth package.

$ wsk action create oauth/github ./openwhisk-passport-auth-0.0.1.js --web true \
        --param auth_provider github \
        --param client_id --client-id-- \
        --param client_secret --client-secret-- \
        --param callback_url https://localhost/api/v1/web/guest/oauth/github.json -i

Then browse to https://localhost/api/v1/web/guest/oauth/github in order to test the action.


Visit to create a new application, or to retrieve the App ID and the App secret for an existing app.

Create a new action called fb inside the oauth package.

$ wsk action create oauth/fb ./openwhisk-passport-auth-0.0.1.js --web true \
        --param auth_provider facebook \
        --param client_id --app-id-- \
        --param client_secret --app-secret-- \
        --param callback_url https://localhost/api/v1/web/guest/oauth/fb.json -i

Then browse to https://localhost/api/v1/web/guest/oauth/fb in order to test the action.


Visit to create an application, or to retrieve the Consumer Key and Consumer Secret for an existing app.

Create a new action called twitter inside the oauth package.

$ wsk action create oauth/twitter ./openwhisk-passport-auth-0.0.1.js --web true \
        --param auth_provider twitter \
        --param client_id --consumer-key-- \
        --param client_secret --consumer-secret-- \
        --param callback_url https://localhost/api/v1/web/guest/oauth/twitter.json -i

Then browse to https://localhost/api/v1/web/guest/oauth/twitter in order to test the action.

Google OAuth

Visit to create a project, or to retrieve the Client ID and Client Secret of an existing application.

NOTE: When configuring credentials in Google select OAuth Client ID, Application Type = Other.

Create a new action called google inside the oauth package.

$ wsk action create oauth/google ./openwhisk-passport-auth-0.0.1.js --web true \
        --param auth_provider google-oauth20 --param auth_provider_name google \
        --param client_id --client-id-- \
        --param client_secret --client-secret-- \
        --param scopes \
        --param callback_url https://localhost/api/v1/web/guest/oauth/google.json -i

Then browse to https://localhost/api/v1/web/guest/oauth/google in order to test the action.

Adding a custom authentication provider

  1. Install the Node module that supports a new provider
  2. Import it in the main action auth.js
  3. Follow the quick start steps

Using Package Bindings

The quick-start method it's easy to setup, but the disadvantage is that the code is uploaded for each individual action/authentication provider. This makes it more difficult to apply changes. OpenWhisk provides a solution for this: package bindings.

With package bindings the action is uploaded and maintained in a single package. Developers may use package binding in order to set custom client_id, client_secret, scope for each authentication provider.

To set this up, start by creating a shared package:

wsk -i package create oauth --shared yes

Then install this action without specifying any default parameters:

wsk -i action create oauth/user ./openwhisk-passport-auth-0.0.1.js  --web true

Then define one or more authentication providers by using package bindings:

wsk -i package bind oauth/user my-oauth-provider \
--param auth_provider <authentication_provider> \
--param client_id <client_id> \
--param client_secret <client_secret> \
--param scopes <comma_sepparated_scopes> \
--param callback_url https://<openwhisk_hostname>/api/v1/web/<openwhisk_namespace>/oauth/fb.json

Linking multiple social IDs together

This action can also be invoked in a sequence with other authentication actions, so that a user can authenticate with multiple providers and at the end to link those identities together. This action is not concerned with persisting user information, but since it receives the HTTP Request first, it does something to help: it creates a context object.

The purpose of the context object is to persist a list with the linked identities during the login process: For example:

  {"provider": "twitter", "user_id": "999"}

This information is assumed to be stored in a cookie named __Secure-auth_context. This cookie can be easily set by an action that is invoked as the last step for the login sequence. See src/action/redirect.js action for an example.


Contributions are welcomed! Read the Contributing Guide for more information.


This project is licensed under the Apache V2 License. See LICENSE for more information.



Last updated on 04 Nov 2019

Did you know?


Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.


Related posts

SocketSocket SOC 2 Logo


  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap


Stay in touch

Get open source security insights delivered straight into your inbox.

  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc