egain-ps-utils is a collection of utility functions designed to simplify common development tasks. This package provides helpers and methods to boost your development workflow, and for the 3.0.0 release, we're offering a convenient jwt authorizer utility for handling authorization-related tasks with dual module support (ESM and CommonJS).

• Dual Module Support: Now supports both ESM (import) and CommonJS (require) syntax
• TypeScript Support: Full TypeScript definitions included
• Requires Node.js 18+ (uses native fetch)
• Improved compatibility and performance
• Updated documentation and usage examples
• Enhanced JWT authorizer utility for Azure AD

• Node.js 18 or higher (uses native fetch)
• ps-chronicle: Use the latest version (^1.0.6 or higher) for best compatibility with this package.

• validateToken: A utility function to assist with authorization checks, ensuring that only authorized users can access specific resources or perform particular actions.

  • This validator will check for:
    1. token expiry
    2. issuer
    3. audience
    4. certificate
  • This function will return a boolean value indicating whether the token is valid or not.

• generateAuthResponse: A utility function to assist with generating authorization responses. This will return a policy document with the effect and the methodArn.

• isTokenIssuedForValidClaimTenantId: A utility function to validate if a token is issued for a valid claim tenant ID.

• AWS Secrets Manager SDK v3 (if using with AWS Lambda and secrets)

Create a secret in AWS Secrets Manager with the following format:

{
    "audience": "xxxx",
    "issuer": "https://xxxx.com/xxxxxx/xx.x"
}

To get the audience and issuer values, you can use the following steps:

1. Get the Metadata from your identity provider.
2. Use these values as the audience and issuer in the secret.

Using npm:

npm install egain-ps-utils

Using yarn:

yarn add egain-ps-utils

import { validateToken, generateAuthResponse, isTokenIssuedForValidClaimTenantId } from 'egain-ps-utils';

const authorize = async (event) => {
  try {
    const authorization = event.headers.Authorization || event.headers.authorization;
    if (!authorization) {
      throw new Error('Authorization token is missing');
    }

    const secretName = 'xxxxx';

    // Validate the token
    const { isTokenValid } = await validateToken(authorization, secretName);
    if (isTokenValid) {
      return generateAuthResponse('Allow', event.methodArn);
    } else {
      return generateAuthResponse('Deny', event.methodArn);
    }
  } catch (error) {
    console.error('Authorization error:', error);
    return generateAuthResponse('Deny', event.methodArn);
  }
};

export { authorize };

const { validateToken, generateAuthResponse, isTokenIssuedForValidClaimTenantId } = require('egain-ps-utils');

const authorize = async (event) => {
  try {
    const authorization = event.headers.Authorization || event.headers.authorization;
    if (!authorization) {
      throw new Error('Authorization token is missing');
    }

    const secretName = 'xxxxx';

    // Validate the token
    const { isTokenValid } = await validateToken(authorization, secretName);
    if (isTokenValid) {
      return generateAuthResponse('Allow', event.methodArn);
    } else {
      return generateAuthResponse('Deny', event.methodArn);
    }
  } catch (error) {
    console.error('Authorization error:', error);
    return generateAuthResponse('Deny', event.methodArn);
  }
};

module.exports = { authorize };

import { validateToken, generateAuthResponse, isTokenIssuedForValidClaimTenantId } from 'egain-ps-utils';

interface LambdaEvent {
  headers: {
    Authorization?: string;
    authorization?: string;
  };
  methodArn: string;
}

const authorize = async (event: LambdaEvent) => {
  try {
    const authorization = event.headers.Authorization || event.headers.authorization;
    if (!authorization) {
      throw new Error('Authorization token is missing');
    }

    const secretName = 'xxxxx';

    // Validate the token
    const { isTokenValid } = await validateToken(authorization, secretName);
    if (isTokenValid) {
      return generateAuthResponse('Allow', event.methodArn);
    } else {
      return generateAuthResponse('Deny', event.methodArn);
    }
  } catch (error) {
    console.error('Authorization error:', error);
    return generateAuthResponse('Deny', event.methodArn);
  }
};

export { authorize };

• This package requires Node.js 18+ for native fetch support.
• For best results, use the latest version of ps-chronicle (at least 1.0.6).
• For Azure AD JWT validation, ensure you provide the correct issuer, audience, and kid in the options object.
• For AWS Lambda usage, ensure your secrets are set up as described above.
• The package automatically detects your module system and provides the appropriate format (ESM or CommonJS).