![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@crossmint/client-sdk-auth
Advanced tools
This SDK provides a set of tools for authenticating users in a Crossmint-powered application on the client-side. It simplifies the process of handling authentication tokens, managing user sessions, and integrating various authentication methods into your
This SDK provides a set of tools for authenticating users in a Crossmint-powered application on the client-side. It simplifies the process of handling authentication tokens, managing user sessions, and integrating various authentication methods into your web applications.
To install the SDK, you can use npm or yarn:
npm install @crossmint/client-sdk-auth
To use the SDK in your application, follow these steps:
import { createCrossmint, CrossmintAuth } from "@crossmint/client-sdk-auth";
const crossmint = createCrossmint({
apiKey: process.env.CLIENT_CROSSMINT_API_KEY || "",
});
const crossmintAuth = CrossmintAuth.from(crossmint);
// Get the current user
const user = await crossmintAuth.getUser();
// Log out the user and clear cookies
crossmintAuth.logout();
To secure the authentication material, you can set up a custom endpoint in your backend that will handle refreshing the authentication material and storing it in HttpOnly cookies. This way, the authentication material is not accessible to JavaScript running in the browser.
In the client, provide the custom refresh route when creating the CrossmintAuth instance:
const crossmintAuth = CrossmintAuth.from(crossmint, {
refreshRoute: "/api/refresh",
});
This way, the SDK will use the provided route to refresh the token instead of the default one and the authentication material can be stored in HttpOnly cookies that are tied to the domain of the provided route.
As you're now using HttpOnly cookies, logout can't happen client-side as it doesn't have access to the cookies. You can set up a custom logout route to handle the logout process.
In the client, provide the custom logout route when creating the CrossmintAuth instance:
const crossmintAuth = CrossmintAuth.from(crossmint, {
logoutRoute: "/api/logout",
});
NOTE: Depending on the framework you're using, you might need to set the whole URL in the refreshRoute
and logoutRoute
options.
You can provide callbacks for token refresh and logout events when creating the CrossmintAuthClient:
const crossmintAuth = CrossmintAuth.from(crossmint, {
callbacks: {
onTokenRefresh: (authMaterial) => {
// Handle new authentication material
},
onLogout: () => {
// Handle logout
},
},
});
{
"jwt": "...",
"refreshToken": "...",
"user": {
"id": "...",
"email": "..."
}
}
These callbacks allow you to perform custom actions when tokens are refreshed or when the user logs out.
FAQs
This SDK provides a set of tools for authenticating users in a Crossmint-powered application on the client-side. It simplifies the process of handling authentication tokens, managing user sessions, and integrating various authentication methods into your
We found that @crossmint/client-sdk-auth demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 8 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
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.