Google OAuth2 OmniAuth Provider for PWSLab Signin/Signup

Google OAuth2 OmniAuth Provider for PWSLab Signin/Signup

To enable the Google OAuth2 OmniAuth provider you must register your application with Google. Google will generate a client ID and secret key for you to use.

Enabling Google OAuth

In Google’s side:
  1. Navigate to the cloud resource manager page
  2. Select Create Project
  3. Provide the project information:
    1. Project name - “PWSLab” works just fine here.
    2. Project ID - Must be unique to all Google Developer registered applications. Google provides a randomly generated Project ID by default. You can use the randomly generated ID or choose a new one.
  4. Refresh the page and you should see your new project in the list
  5. Go to the Google API Console
  6. Select the previously created project form the upper left corner
  7. Select Credentials from the sidebar
  8. Select OAuth consent screen and fill the form with the required information
  9. In the Credentials tab, select Create credentials > OAuth client ID
  10. Fill in the required information
    1. Application type - Choose “Web Application”
    2. Name - Use the default one or provide your own
    3. Authorized JavaScript origins -This isn’t really used by PWSLab but go ahead and put https://companyname.pwslab.net/
      Authorized redirect URIs - Enter your domain name followed by the callback URIs one at a time:
      https://companyname.pwslab.net/users/auth/google_oauth2/callback https://companyname.pwslab.net/-/google_api/auth/callback
You should now be able to see a Client ID and Client secret. Note them down or keep this page open as you will need them later.

To enable projects to access Google Kubernetes Engine, you must also enable these APIs:
  1. Google Kubernetes Engine API
  2. Cloud Resource Manager API
  3. Cloud Billing API
In PWSLab's side:
    Now, simply raise a PWSLab GDS Support Request to do the backend-configuration in your private PWSLab instance. Login to https://support.peerxp.com/ with your work email to raise the request, and share the Client ID and Client Secret. 

    Within 24 hours, on the sign in page there should now be a Google icon below the regular sign in form.

    Click the icon to begin the authentication process. Google will ask the user to sign in and authorize the PWSLab application. If everything goes well the user will be returned to PWSLab and will be signed in.


    Have more questions? Please email us at support@peerxp.com
    Also, let us know if the article is helpful!

      • Related Articles

      • List of PWSLab CI/CD Environment Variables

        Introduction This document enlists a set of pre-defined environment variables accepted by PWSLab CI/CD for the local environment of the Runner. These can be referenced directly in the .pwslab.yml file or via the Project's Settings > CI/CD > ...
      • PWSLab Git Workshop - Useful commands and concepts

        Agenda A brief history of Git. PWSLab walkthrough. Configure your environment. Workshop. Git Introduction Visit: https://git-scm.com/about Distributed version control. It does not rely on a connection to a central server. Many copies of the complete ...
      • How to install and setup Ngrok for private PWSLab installations? (updated 2019)

        Introduction Ngrok is one of the most popular tunnel service platform through which you can easily expose your local servers (like PWSLab installations) which are behind NATs/Firewalls to the public internet over secure tunnels. It connects to the ...
      • Billing Policy for PWSLab Accounts

        Introduction PeerXP offers a DevOps as a Service solutions for enterprises - PWSLab. Pricing plans are based on the number of users/projects for different PWSLab products and services.  If your team doesn't fit neatly into one of the Pricing plan ...
      • PWSLab External User License Policy

        Introduction The External User License Policy is primarily for the benefit of customers who want to add temporary External users in PWSLab. This is offered because we don’t want you to follow a cumbersome or inefficient way of accepting external code ...