OAuth connection

How to set up your own OAuth connection to login to to Nudj.

Integrate your users through OAuth Connection

Allows for seamless login and access to scoped APIs which you might require us to push data, i.e., a new coupon, etc. - This is how we integrated with United

Our platform supports SAML and other Single Sign-On (SSO) methods using OpenID Connect. Clients can provide us with a configuration containing the clientId, clientSecret, and their well-known configuration URL/domain to enable these integrations.

  • Data we will require is listed below:
    • UserId
    • User Email
    • Username (optional)
    • Locale (optional)

Passing data back: Once users are authenticated, we are able to link data in the background and push rewards such as loyalty points/stamps back into the customer's system via API. Requirements:

  • Scoped API Endpoints secured via user-level OAuth access_token or client-level (Nudj) API token

User Journeys

Scenario A - User lands directly on LQ WW branded site

  • The site will be fully branded to WW as well as the site URL
  • User will be able to see community and challenge information
  • Upon trying to participate, i.e., start a challenge, they will be prompted with a login modal containing the WW Login Option
  • On clicking login, the OAuth flow would begin, i.e., they are redirected to the WW Auth site where they securely sign in (or sign up if they don’t have an account) and are sent back to the LQ WW site
  • User is now authenticated to the LQ WW site with their account connected to their WW account allowing for syncing of data

Scenario B - User clicks a magic link embedded within a banner on the WW Site

  • Is the user logged in on the WW site?
    • YES:
      • They would automatically be logged into the LQ WW Site and can participate immediately in challenges
    • NO:
      • Before loading the LQ WW page, they will immediately be sent to the WW login page
      • Upon login, they would then be redirected back to the LQ WW page logged in as mentioned in Scenario A.
      • This flow would only trigger if the banner is shown to an unauthenticated user - not recommended
  • What’s the point?: You can provide the user's OAuth id_token/access_token on the URL and log them in automatically, removing a friction point

New Features

  • Support for embedding iFrames within your own site has been added.
  • Single-page challenges for QR code scanning or placing behind a banner/link are also supported
  • Connect to the Nudj API to pull data with an Organisation scoped API Key
  • Provide Nudj with access to your API for any integration needs
Did this answer your question?
😞
😐
🤩