Introduction

This sample builds upon Apigee's excellent oauth andvanced sample sample project, which demonstrates how to implement OAuth2 Authorization Code flow with Apigee. We have modified the sample by "replacing" the Node.js "login-app" with Okta. Apigee is still the OAuth2 Authorization Server for the client (app), but at a high level it is now also an "OpenID Connect Client" authenticating into Okta (the "IdP"), i.e. Authentication is being delegated to Okta. You get to leverage Okta's enterprise grade security Identity Management features; Just some of the things you can do with Okta include:

• Add Social Auth capabilities to your application
• Seamlessly connect to an 3rd party SAML and OpenID Connect IdPs
• Provide MFA
• Logging of all events ...All without writing a single line of code.

Below is a diagram describing the modified flow:

Prerequisites

Tools

To run this sample, you'll need:

• node.js and npm installed

• Yeoman installed

• apigeetool installed

Apigee Account

• The Admin username and password that you use to login to enterprise.apigee.com.

• The name of the organization in which you have an account. Login to enterprise.apigee.com and check account settings.

• Create a cache resource in the Environment you wish to deploy with the cache name cache1

Okta Account

• Sign up for a free Developer Account developer.okta.com

Register an OpenID Connect Client (the "Apigee" Client)

• Once you have access to the Developer Console, from there create an OpenID Connect client:

  • From the menu options, navigate to Applications > Add Application > Web
  • Provide a name for your app, e.g. Apigee-Client
  • Leave Base URI as-is
  • IMPORTANT: Enter the "Login redirect URI" with the value https://{myorg}-{myenv}.apigee.net/okta-oidc/callback. For example, If myorg == "okta_oidc", and I am deploying to the "test" environment, then the redirect URI is https://okta_oidc-test.apigee.net/okta-oidc/callback
  • Click through to complete the App setup
  • Once complete, you can find the client_id and client_secret in the "General" tab. You will need these values when you run the Yeoman tool

• Please note that the sample does not run properly in Windows 10. Please run in macOS or Linux for full compatibility.

Deploying

1. Create a directory and 'cd' into it e.g.

> mkdir example-project
> cd example-project

2. Clone this repository into the directory you just created

> git clone [email protected]:zeekhoo-okta/generator-okta-oidc-apigee.git

3. 'cd' into the "generator" directory:

> cd generator-okta-oidc-apigee

4. Install dependencies

> npm install

5. In order to run the Yeoman tool, you'll need to symlink this local module to a global one using this command:

> npm link

This will install your project dependencies and symlink a global module to your local file. After npm is done, you will be able to call yo generator-name

6. Call Yeoman: yo okta-oidc-apigee

7. Follow the prompts:

Sample Generator of OAuth Authorization Code Grant Type Proxies.
? Your Apigee admin username:
? Your Apigee admin password:
? Apigee API Proxy Base Url: https://[organization]-[environment].apigee.net
? Apigee Organization Name: [organization]
? Apigee Environment Name: [environment]
? Management API URL Endpoint: https://api.enterprise.apigee.com
? Your Okta "Org": dev-######.oktapreview.com
? The CLIENT_ID of the app you created in Okta:
? The CLIENT_SECRET of the app you created in Okta:
? Id of the AuthorizationServer you configured to use in Okta (your Developer account comes with a pre-configured "default" AS): default

Note: Obtain the CLIENT_ID and CLIENT_SECRET values from the App you registered in Okta from previous steps. Your Okta account should have a "default" AuthorizationServer so use that value if you're new to Okta.

Running the sample

1. Open a browser and navigate to the sample "web application":

   http://myorg-myenv.apigee.net/web

   For example:

   http://okta_oidc-test.apigee.net/web

2. Initiate the flow. Just click the [Apigee+Okta Example Login] button. This action sends a request to the /oauth2/authorize proxy endpoint, initiating OAuth2. The AuthorizationServver (Apigee) which redirects the browser to Okta for login.

Implicit flow example

By default, this sample demonstrates the authorization code (3-legged OAuth) flow but it can also do Implicit flow. To see implicit flow, change the request behind the [Apigee+Okta Example Login] button to request the authorize endpoint with response_type=token instead of response_type=code

• You can do this by editing the webserever-app proxy's HTMLIndex policy; by changing the button's function call to:

function login()
         {
            window.location.href=BASEURL+'/oauth2/authorize?client_id='+CLIENT_ID+'&redirect_uri='+REDIRECT+'&response_type=token&scope=foo&state=bar';
         }