npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

psi-auth

v1.0.9

Published

ProServe Innovation team JWKS integration

Downloads

526

Readme

psi-auth

Seamlessly integrate with RingCentral Professional Services's JWKS solution.

Getting started

Install the package

npm install @ringcentral-pro-serv/psi-auth

Initializing JWKS

Before using PSi Auth, you'll need to initialize it by calling initializeJWKS(). Here's an example:

initializeJWKS({
    url: `${process.env.JWKS_BASE_URL}/api/v1/public/token`,
    localCacheTtl: 10,
    localCaching: true,
    remoteCaching: true,
    jwt: process.env.JWKS_JWT,
    clientId: process.env.LOCAL_JWKS_CLIENT_ID,
    clientSecret: process.env.LOCAL_JWKS_CLIENT_SECRET
})

In the example above, PSi Auth is being initialized for local development. The giveaway here is the inclusion of the jwt, clientId, and clientSecret options. PSi Auth uses those values to facilitate the use of the public authentication endpoint.

Here's an example of initialization in production:

initializeJWKS({
    url: `${process.env.JWKS_BASE_URL}/api/v1/token`,
    localCacheTtl: 15,
    localCaching: true,
    remoteCaching: true
})

Getting access tokens

Getting an access token with PSi Auth is simple, just call getToken() and supply the appName and accounted.

const token = await getToken({
    appName: 'exampleApp',
    accountId: '62904886028'
})

Depending on how you initialized PSi Auth, you may receive a cached token, as such, you should make note of the expires_at property of the returned object. JWKS sets this to the true expiration of the token. JWKS does not alter the expires_in property returned by the RC platform, so it may not be accurate.

Here's an example response:

{
    "access_token": "U0pDMDFQMTNQQVMwM... truncated for brevity",
    "token_type": "bearer",
    "expires_in": 3600,
    "refresh_token": "U0pDMDFQMTNQQVMwMHxBQU... truncated for brevity",
    "refresh_token_expires_in": 604800,
    "scope": "ReadAccounts",
    "owner_id": "305655028",
    "endpoint_id": "ehhhoi3MRAGvu3wu2ALJpg",
    "session_id": "10bb4cc8-ed66-426b-886d-8f9259eff804",
    "session_idle_timeout": 30,
    "issued_at": 1716217482,
    "expires_at": 1716221082,
    "refresh_token_expires_at": 1716822282
}