
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
@kinde/infrastructure
Advanced tools
Types and methods to work with Kinde Infrastructure features
# npm
npm install @kinde/infrastructure
# yarn
yarn add @kinde/infrastructure
# pnpm
pnpm install @kinde/infrastructure
idTokenCustomClaims - Define and set custom claims on the id token
accessCustomClaims - Define and set custom claims on the access token
m2mCustomClaims - Define and set custom claims on the m2m token
denyAccess - Deny access to your application
fetch - Sent a request to external API
secureFetch - Sent an encypted request to external API
getEnvironmentVariable - Get Environment variable from Kinde secrets
createKindeAPI - Create handler to call the Kinde management SDK
denyPlanSelection - Deny a plan selection change
denyPlanCancellation - Deny cancellion of a plan
getM2MToken - Get a m2m token, this will cache for the lifespan of the token for other workflows to use
getKindeWidget - Places the kinde widget on the page
getKindeNonce - Places the generated Nonce on your page for increased security
getKindeRequiredCSS - Inserts the required CSS
getKindeRequiredJS - Inserts the required JS
getKindeCSRF - Places the generated CSRF on your page for increased security
getKindeRegisterUrl or getKindeSignUpUrl - Gets the registration Url
getKindeLoginUrl or getKindeSignInUrl- Gets the login Url
getLogoUrl - Gets the organisations logo Url
getDarkModeLogoUrl - gets the organisations dark mode logo Url
getSVGFaviconUrl - gets the organistaions SVG favicon
getFallbackFaviconUrl - gets the organisations fallback favicon
getKindeThemeCode - Get the theme code
setKindeDesignerCustomProperties - Update styling of the Kinde widget
{
"request": {
"ip": "1.2.3.4",
"auth": {
"audience": ["https://api.example.com/v1"]
}
},
"context": {
"auth": {
"origin": "refresh_token_request",
"connectionId": "conn_0192b...",
"isExistingSession": false
},
"user": {
"id": "kp_6a071...",
"identityId": "identity_0192c..."
},
"domains": {
"kindeDomain": "https://mykindebusiness.kinde.com"
},
"workflow": {
"trigger": "user:tokens_generation"
},
"application": {
"clientId": "f77dbc..."
},
"organization": {
"code": "org_b5a9c8..."
}
}
}
{
"request": {
"ip": "1.2.3.4",
"auth": {
"audience": ["https://api.example.com/v1"]
}
},
"context": {
"domains": {
"kindeDomain": "https://mykindebusiness.kinde.com"
},
"workflow": {
"trigger": "m2m:tokens_generation"
},
"application": {
"clientId": "f77dbc..."
}
}
}
{
"request": {
"ip": "1.2.3.4",
"auth": {
"audience": ["https://api.example.com/v1"]
}
},
"context": {
"auth": {
"firstPassword": "somesecurepassword",
"secondPassword": "somesecurepassword",
"newPasswordReason": "reset"
},
"domains": {
"kindeDomain": "https://mykindebusiness.kinde.com"
},
"workflow": {
"trigger": "user:new_password_provided"
},
"application": {
"clientId": "f77dbc..."
}
}
}
{
"request": {
"ip": "1.2.3.4",
"auth": {
"audience": ["https://api.example.com/v1"]
}
},
"context": {
"auth": {
"password": "somesecurepassword"
},
"domains": {
"kindeDomain": "https://mykindebusiness.kinde.com"
},
"workflow": {
"trigger": "user:existing_password_provided"
},
"application": {
"clientId": "f77dbc..."
}
}
}
kinde.accessToken
import {
onUserTokenGeneratedEvent,
getKindeAccessTokenHandle,
WorkflowSettings,
WorkflowTrigger,
} from "@kinde/infrastructure";
export const workflowSettings: WorkflowSettings = {
id: "addAccessTokenClaim",
trigger: WorkflowTrigger.UserTokenGeneration,
bindings: {
"kinde.accessToken": {},
},
};
export default async function (event: onUserTokenGeneratedEvent) {
const accessToken = accessTokenCustomClaims<{
hello: string;
ipAddress: string;
}>();
accessToken.hello = "Hello there!";
accessToken.ipAddress = event.request.ip;
},
This will result with two new extra claims added to the AccessToken
{
"hello": "Hello there!",
"ipAddress": "1.2.3.4"
}
This example will prevent login from anyone accessing with an IP address starting with 192
kinde.accessToken
export default async function (event: onUserTokenGeneratedEvent) {
if (event.request.ip.startsWith("192")) {
denyAccess("You are not allowed to access this resource");
}
}
This example will get the api token from the Kinde environment variables and call an API to get the timezone for the IP address and add it to the ID token
kinde.idToken
kinde.fetch
kinde.env
url
export default async function (event: onUserTokenGeneratedEvent) {
const ipInfoToken = getEnvironmentVariable("IP_INFO_TOKEN")?.value;
const { data: ipDetails } = await fetch(
`https://ipinfo.io/${event.request.ip}?token=${ipInfoToken}`,
{
method: "GET",
responseFormat: "json",
headers: {
"Content-Type": "application/json",
},
},
);
const idToken = idTokenCustomClaims<{
timezone: string;
}>();
idToken.timezone = ipDetails.timezone;
}
In order to use the Kinde management API you will need to first configure an application within Kinde and grant it access to the Kinde Management API with the desired scopes.
By default the createKindeAPI method initially look up the following environment variables setup in Kinde settings to determine the application to use.
KINDE_WF_M2M_CLIENT_IDKINDE_WF_M2M_CLIENT_SECRET - Ensure this is setup with sensitive flag enabled to prevent accidental sharingcreateKindeAPI can also accept an additional parameter which can contain clientID/clientSecret or clientIDKey/clientSecretKey which can define the environment variables to lookup
The example below will read the users permissions and add them to the accessToken
kinde.accessToken
kinde.fetch
kinde.env
url
export default async function (event: onUserTokenGeneratedEvent) {
const orgCode = event.context.organization.code;
const userId = event.context.user.id;
const kindeAPI = await createKindeAPI(event);
const { data: res } = await kindeAPI.get({
endpoint: `organizations/${orgCode}/users/${userId}/permissions`,
});
const accessToken = accessTokenCustomClaims<{ hello: string; settings: string; permissions: []}>();
accessToken.hello = "Hello there!";
accessToken.permissions = res.permissions;
},
[!WARNING] Some claims are prohibited to be updated from a workflow. (see Prohibited Claims)
No sensitive data should be added to tokens as these can be accessed publically
Kinde Documentation - Explore the Kinde docs
If you'd like to contribute to this project, please follow these steps:
By contributing to Kinde, you agree that your contributions will be licensed under its MIT License.
FAQs
## Description
We found that @kinde/infrastructure demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer 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
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.