@jfront/oauth-core
Advanced tools
Core functionality for OAuth 2.0 connection.
import { OAuth } from "@jfront/oauth-core"
const oauth = new OAuth(
"clientId",
"http://localhost/app/oauth",
"http://localhost/authorize",
"http://localhost/token",
"http://localhost/logout",
window.sessionStorage,
)
Authorization Code/Implicit flow authorization.
oauth.authorize("code", "http://localhost/app/view")
Get token with authorization code, when authorization step was completed.
oauth.getTokenWithAuthCode("authorization_code", "random_nonce_string")
Refresh access token, if you have refresh_token.
oauth.refreshToken("refresh_token")
Get token with user login/password.
oauth.getTokenWithUserCredentials("login", "password")
Logout for client-side apps.
oauth.getTokenWithUserCredentials("http://localhost/app/view")
FAQs
Core functionality for OAuth 2.0 connection.
The npm package @jfront/oauth-core receives a total of 0 weekly downloads. As such, @jfront/oauth-core popularity was classified as not popular.
We found that @jfront/oauth-core demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."