TypeScript/JavaScript client library for OADA identity. Can be used both in NodeJS and in the browser.

For use in NodeJS or with something like webpack:

yarn add @oada/id-client

The code to use in the browser can be generated with the following command:

yarn bundle

This will create the file bundle.js.

• On Server Example
• In Browser Example

This version of the library wraps the core functionality for easy use in typical Node.JS uses.

It will pop up a window using the default browser to take the user through the needed flows and the return the resulting token(s).

Asynchronous function for generating an ID token request against an OADA identity provider.

domain string of domain with which to log in the user.

options object containing at least the following properties:

• metadata object containing client metadata, or string of a software_statement JWT
• privateKey a private JWK for use in the JWT bearer client auth (required for code flow)
• params Optional OpenID Connect parameters placed in params as string properties will be used (e.g. display, prompt, login_hint)

Optional OpenID Connect parameters placed in options as string properties will be used (e.g. display, prompt, login_hint).

const options = {
  metadata: {
    /* See spec linked above */
  },
};

const domain = /* Set domain based on text box, dropdown, etc. */;

// Promise will resolve after user completes the flow in the browser
const idToken = await oadaIdClient.getIDToken(domain, options);
console.dir(idToken);

Asynchronous function for generating an access token request against an OADA compliant API.

domain string of domain from which to get an OADA API access token. The value passed to the function can be overridden by a query or form parameter with a name of domain.

options object containing at least the following properties:

• metadata object containing client metadata, or string of a software_statement JWT
• scope space separated string of OAuth scopes for the request access token to have.
• privateKey a private JWK for use in the JWT bearer client auth (required for code flow)
• params Optional OpenID Connect parameters placed in params as string properties will be used (e.g. display, prompt, login_hint)

const options = {
  metadata: {
    /* See spec linked above */
  },
  scope: 'some.oada.defined.scope',
};

const domain = /* Set domain based on text box, dropdown, etc. */;

// Promise will resolve after user completes the flow in the browser
const accessToken = await oadaIdClient.getAccessToken(domain, options);
console.dir(accessToken);

This version of the library wraps the core functionality for use as connect style "middleware". This can be used in a Node.JS server using a compatible web development framework, such as express.

For a working example of using this wrapper, see the on server example.

Middleware for generating an ID token request against an OADA identity provider.

domain string of domain with which to log in the user. The value passed to the function can be overridden by a query or form parameter with a name of domain.

options object containing at least the following properties:

• metadata object containing client metadata, or string of a software_statement JWT
• privateKey a private JWK for use in the JWT bearer client auth (required for code flow)
• params Optional OpenID Connect parameters placed in params as string properties will be used (e.g. display, prompt, login_hint)

const options = {
  metadata: {
    /* See spec linked above */
  },
  privateKey: {
    pem: fs.readFileSync('/path/to/key.pem'),
    kid: 'key_id_corresponding_to_pem',
  },
};

app.use(
  '/getIdToken',
  oadaIdClient.getIDToken('some.oada-identity-provider.com', options)
);

Middleware for generating an access token request against an OADA compliant API.

domain string of domain from which to get an OADA API access token. The value passed to the function can be overridden by a query or form parameter with a name of domain.

options object containing at least the following properties:

• metadata object containing client metadata, or string of a software_statement JWT
• privateKey a private JWK for use in the JWT bearer client auth (required for code flow)
• scope space separated string of OAuth scopes for the request access token to have.
• params Optional OpenID Connect parameters placed in params as string properties will be used (e.g. display, prompt, login_hint)

const options = {
  metadata: {
    /* See spec linked above */
  },
  privateKey: {
    pem: fs.readFileSync('/path/to/key.pem'),
    kid: 'key_id_corresponding_to_pem',
  },
  scope: 'some.oada.defined.scope',
};

app.use(
  '/getAccessToken',
  oadaIdClient.getAccessToken('some.oada-cloud-provider.com', options)
);

Middleware for handling redirects from getIDToken or getAccessToken middlewares. In most cases, you will apply this middleware in two locations, one to receive getIDToken redirects and another to receive getAccessToken redirects.

// Handle ID token redirects
app.use(
  '/url/referenced/by/getIDToken/redirect_uri',
  oadaIdClient.handleRedirect()
);
app.use(
  '/url/referenced/by/getIDToken/redirect_uri',
  function (req, res, next) {
    // ID token is in req.token
    console.dir(req.token);
  }
);

// Handle access token redirects
app.use(
  '/url/referenced/by/getAccessToken/redirect_uri',
  oadaIdClient.handleRedirect()
);
app.use(
  '/url/referenced/by/getAccessToken/redirect_uri',
  function (req, res, next) {
    // Access token is in req.token
    console.dir(req.token);
  }
);

This version of the library wraps the core functionality for easy use in the browser.

For a working example of using this wrapper, see the in browser example.

Asynchronous function for generating an ID token request against an OADA identity provider.

domain string of domain with which to log in the user.

options object containing at least the following properties:

• metadata object containing client metadata, or string of a software_statement JWT
• params Optional OpenID Connect parameters placed in params as string properties will be used (e.g. display, prompt, login_hint)

Optional OpenID Connect parameters placed in options as string properties will be used (e.g. display, prompt, login_hint).

const options = {
  metadata: {
    /* See spec linked above */
  },
};

const domain = /* Set domain based on text box, dropdown, etc. */;

const idToken = await oadaIdClient.getIDToken(domain, options);
console.dir(idToken);

Asynchronous function for generating an access token request against an OADA compliant API.

domain string of domain from which to get an OADA API access token. The value passed to the function can be overridden by a query or form parameter with a name of domain.

options object containing at least the following properties:

• metadata object containing client metadata, or string of a software_statement JWT
• scope space separated string of OAuth scopes for the request access token to have.
• params Optional OpenID Connect parameters placed in params as string properties will be used (e.g. display, prompt, login_hint)

const options = {
  metadata: {
    /* See spec linked above */
  },
  scope: 'some.oada.defined.scope',
};

const domain = /* Set domain based on text box, dropdown, etc. */;

const accessToken = await oadaIdClient.getAccessToken(domain, options);
console.dir(accessToken);

Function for handling redirects generated by getIDToken or getAccessToken function. Simply needs to be called by the page served from the URL corresponding to redirect_uri.

<!-- Page served at redirect_uri for getIDToken and/or getAccessToken -->
<html>
  <head>
    <script src="path/to/library/browser/code.js"></script>
    <script>
      oadaIdClient.handleRedirect();
    </script>
  </head>
</html>

Not yet documented.

1. OpenID Connect Core 1.0
2. OAuth 2.0 Authorization Framework
3. JSON Web Key (JWK) Draft 31
4. OAuth 2.0 Dynamic Client Registration Protocol