
Research
/Security News
Weaponizing Discord for Command and Control Across npm, PyPI, and RubyGems.org
Socket researchers uncover how threat actors weaponize Discord across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
ic-use-internet-identity
Advanced tools
Hook that makes it easy to integrate IC Internet Identity into your React application.
Internet Identity is an authentication service running on the Internet Computer. It allows users to create an identity that can be used to authenticate with canisters (smart contracts) running on the Internet Computer.
ic-use-internet-identity
is a hook that makes it easy to integrate Internet Identity into your React application. It provides a simple interface for logging in and out with the Internet Identity service.
ensureInitialized()
and isAuthenticated()
for use outside React (examples use TanStack Router).pnpm install ic-use-internet-identity
The hook also requires the following @dfinity/x
packages to be installed with a version of at least 3.1.0
:
pnpm install @dfinity/agent @dfinity/auth-client @dfinity/identity @dfinity/candid
[!TIP] For a complete example, see the ic-use-internet-identity-demo demo project.
To use ic-use-internet-identity
in your React application, follow these steps:
InternetIdentityProvider
componentWrap your application's root component with InternetIdentityProvider
to provide all child components access to the identity context.
// main.tsx
import { InternetIdentityProvider } from "ic-use-internet-identity";
import React from "react";
import ReactDOM from "react-dom/client";
ReactDOM.createRoot(document.getElementById("root")!).render(
<React.StrictMode>
<InternetIdentityProvider>
<App />
</InternetIdentityProvider>
</React.StrictMode>
);
[!TIP] Identity Provider Configuration: The library defaults to using the main Internet Identity instance at
https://identity.ic0.app
. You can override this by setting theidentityProvider
in yourloginOptions
.
- Default:
https://identity.ic0.app
(used automatically)- Custom via loginOptions: Pass
identityProvider
inloginOptions
prop- Local development:
http://${CANISTER_ID_INTERNET_IDENTITY}.localhost:4943
Configure via loginOptions
<InternetIdentityProvider loginOptions={{ identityProvider: process.env.DFX_NETWORK === "local" ? `http://${process.env.CANISTER_ID_INTERNET_IDENTITY}.localhost:4943` : "https://identity.ic0.app" }} > <App /> </InternetIdentityProvider>
login()
function to a buttonThe login()
function initiates the Internet Identity authentication process. Here's what happens when you call it:
status
immediately changes to "logging-in"
and remains there until the process completesstatus
becomes "success"
, identity
is populated, and the popup closesstatus
becomes "error"
and error
contains the error details[!WARNING] User Interaction Required: The
login()
function MUST be called in response to a user interaction (e.g., button click). Calling it inuseEffect
or similar will fail because browsers block popup windows that aren't triggered by user actions.
[!IMPORTANT] No Promise Handling Required: The
login()
function returnsvoid
and handles all results through the hook's state. Monitor thestatus
,error
, andidentity
values returned by the hook instead of using try/catch blocks.
The login process follows a predictable status flow:
"initializing"
→ Library is loading and checking for existing authentication"idle"
→ Ready to login"logging-in"
→ Login popup is open, user is authenticating"success"
→ Login completed successfully, identity
is available"error"
→ Login failed, check error
for detailsUse the status
and error
state variables to track the login process and provide appropriate UI feedback:
// LoginButton.tsx
import { useInternetIdentity } from "ic-use-internet-identity";
export function LoginButton() {
const { login, status, error, isError, identity } = useInternetIdentity();
const renderButton = () => {
switch (status) {
case "initializing":
return (
<button disabled>
⏳ Initializing...
</button>
);
case "idle":
return (
<button onClick={login}>
Login with Internet Identity
</button>
);
case "logging-in":
return (
<button disabled>
🔄 Logging in...
</button>
);
case "success":
return (
<button disabled>
✅ Logged in as {identity?.getPrincipal().toString().slice(0, 8)}...
</button>
);
case "error":
return (
<button onClick={login}>
🔄 Retry Login
</button>
);
default:
return null;
}
};
return (
<div>
{renderButton()}
{isError && (
<div style={{ color: "red", marginTop: "8px" }}>
❌ Login failed: {error?.message}
</div>
)}
</div>
);
}
The hook also provides convenient boolean properties for common status checks:
const {
isInitializing, // status === "initializing"
isIdle, // status === "idle"
isLoggingIn, // status === "logging-in"
isLoginSuccess, // status === "success"
isError // status === "error"
} = useInternetIdentity();
// Example usage
if (isInitializing) {
// Show initial loading state
}
if (isLoggingIn) {
// Show login spinner
}
if (isLoginSuccess && identity) {
// User is authenticated, show protected content
}
identity
context variable to access the identityThe identity
context variable contains the identity of the currently logged in user. The identity is available after successfully loading the identity from local storage or completing the login process.
The preferred way to use the identity is to connect it to the ic-use-actor hook. The hook provides a typed interface to the canister methods as well as interceptor functions for handling errors etc.
// Actors.tsx
import { ReactNode } from "react";
import {
ActorProvider,
createActorContext,
createUseActorHook,
} from "ic-use-actor";
import {
canisterId,
idlFactory,
} from "path-to/your-service/index";
import { _SERVICE } from "path-to/your-service.did";
import { useInternetIdentity } from "ic-use-internet-identity";
const actorContext = createActorContext<_SERVICE>();
export const useActor = createUseActorHook<_SERVICE>(actorContext);
export default function Actors({ children }: { children: ReactNode }) {
const { identity } = useInternetIdentity();
return (
<ActorProvider<_SERVICE>
canisterId={canisterId}
context={actorContext}
identity={identity}
idlFactory={idlFactory}
>
{children}
</ActorProvider>
);
}
{
/** Options for creating the {@link AuthClient}. See AuthClient documentation for list of options
*
*`ic-use-internet-identity` defaults to disabling the AuthClient idle handling (clearing identities
* from store and reloading the window when user is idle). If that behaviour is preferred, set these settings:
*
* ```
* const options = {
* idleOptions: {
* disableDefaultIdleCallback: false,
* disableIdle: false,
* },
* }
* ```
*/
createOptions?: AuthClientCreateOptions;
/** Options that determine the behaviour of the {@link AuthClient} login call. These options are a subset of
* the {@link AuthClientLoginOptions}. */
loginOptions?: LoginOptions;
/** Clear the identity automatically on expiration. Default value is `true`. */
clearIdentityOnExpiry?: boolean;
/** The child components that the InternetIdentityProvider will wrap. This allows any child
* component to access the authentication context provided by the InternetIdentityProvider. */
children: ReactNode;
}
The LoginOptions
interface extends AuthClientLoginOptions
from @dfinity/auth-client
with some modifications:
import type { AuthClientLoginOptions } from "@dfinity/auth-client";
export interface LoginOptions
extends Omit<
AuthClientLoginOptions,
"onSuccess" | "onError" | "maxTimeToLive"
> {
/**
* Expiration of the authentication in nanoseconds
* @default BigInt(3_600_000_000_000) nanoseconds (1 hour)
*/
maxTimeToLive?: bigint;
}
This means you can use all properties from AuthClientLoginOptions
except onSuccess
, onError
. Available properties include:
identityProvider?: string | URL
- Identity provider URL (defaults to https://identity.ic0.app
)maxTimeToLive?: bigint
- Session expiration (defaults to 1 hour)allowPinAuthentication?: boolean
- Allow PIN/temporary key authenticationderivationOrigin?: string | URL
- Origin for delegated identity generationwindowOpenerFeatures?: string
- Popup window configurationcustomValues?: Record<string, unknown>
- Extra values for login requestexport type Status =
| "initializing"
| "idle"
| "logging-in"
| "success"
| "error";
export type InternetIdentityContext = {
/** The identity is available after successfully loading the identity from local storage
* or completing the login process. */
identity?: Identity;
/** Connect to Internet Identity to login the user. */
login: () => void;
/** Clears the identity from the state and local storage. Effectively "logs the user out". */
clear: () => void;
/** The status of the login process. Note: The login status is not affected when a stored
* identity is loaded on mount. */
status: Status;
/** `status === "initializing"` */
isInitializing: boolean;
/** `status === "idle"` */
isIdle: boolean;
/** `status === "logging-in"` */
isLoggingIn: boolean;
/** `status === "success"` */
isLoginSuccess: boolean;
/** `status === "error"` */
isError: boolean;
/** Login error. Unsurprisingly. */
error?: Error;
};
The library handles all errors through its state management system. You don't need try/catch blocks - simply monitor the error
and isError
state:
import { useInternetIdentity } from "ic-use-internet-identity";
export function LoginComponent() {
const { login, error, isError, status } = useInternetIdentity();
return (
<div>
<button
onClick={login}
disabled={status === "logging-in"}
>
{status === "logging-in" ? "Logging in..." : "Login"}
</button>
{isError && (
<div style={{ color: "red" }}>
Login error: {error?.message}
</div>
)}
</div>
);
}
When using ic-use-internet-identity
with routing libraries (for example, TanStack Router), it's recommended to handle the initialization phase before allowing navigation to protected routes. The library exports utility functions that work outside of React components and can be used with many routing libraries — TanStack Router is shown here as an example.
// Wait for the identity initialization to complete and get restored identity
ensureInitialized(): Promise<Identity | undefined>
// Check if user is authenticated
isAuthenticated(): boolean
// Get the current identity
getIdentity(): Identity | undefined
Here's how to protect routes (example: TanStack Router):
import { createRoute, redirect } from "@tanstack/react-router";
import { ensureInitialized, isAuthenticated } from "ic-use-internet-identity";
// Protected route example
const dashboardRoute = createRoute({
getParentRoute: () => rootRoute,
path: "dashboard",
beforeLoad: async () => {
const identity = await ensureInitialized();
if (!identity) {
throw redirect({ to: "/login" });
}
},
component: DashboardComponent,
});
Note: beforeLoad
is executed during navigation and does not re-run when authentication state changes. If a user signs out after a route has already loaded, the beforeLoad
hook will not be invoked again. To handle dynamic changes in authentication (for example, user-initiated sign out), provide a React component that observes the hook and reacts to changes at runtime.
import { useRouter } from "@tanstack/react-router";
import { useInternetIdentity } from "ic-use-internet-identity";
import { useEffect } from "react";
export function AuthGuard() {
const router = useRouter();
const { identity } = useInternetIdentity();
useEffect(() => {
if (!identity) {
void router.invalidate() // This forces beforeLoad to be re-run and user directed to login page
}
}, [identity, router]);
return null;
}
For multiple protected routes you can extract a small beforeLoad
helper and use file-route helpers (the example below uses TanStack Router). Below are two patterns: a simple authenticateRoute()
helper and an example showing how to create a protected file route with createFileRoute
.
// authenticateRoute helper function: src/lib/authenticate-route.ts
import { isRedirect, redirect } from "@tanstack/react-router";
import { ensureInitialized } from "ic-use-internet-identity";
export async function authenticateRoute() {
try {
const identity = await ensureInitialized();
if (!identity) {
// No identity -> redirect to login
// eslint-disable-next-line @typescript-eslint/only-throw-error
throw redirect({ to: "/login" });
}
// Additional initialization, authenticate actor, etc.
} catch (err) {
if (isRedirect(e)) throw e // Re-throw if error is a redirect
console.error("Identity initialization failed:", err);
// Initialization error — redirect to an error page
// eslint-disable-next-line @typescript-eslint/only-throw-error
throw redirect({ to: "/error" });
}
}
// Example file route: src/routes/about.tsx
import { createFileRoute } from "@tanstack/react-router";
import { authenticateRoute } from "../lib/authenticate-route";
import About from "../components/About";
export const Route = createFileRoute("/about")({
beforeLoad: async () => authenticateRoute(),
component: About,
});
Always await initialization: The ensureInitialized()
function ensures the library has finished checking for cached identities before making routing decisions.
Double-check in components: beforeLoad
runs once during navigation and does not react to later authentication changes (for example, when a user signs out). Use the useInternetIdentity
hook in your components — or the AuthGuard
component above — to observe auth state changes and perform redirects or show fallback UI.
Handle loading states: During initialization (< 1 second), consider showing a loading spinner or splash screen.
Redirect patterns: You can either redirect to a login page or let components handle the unauthenticated state based on your UX preferences.
identity
for changes and handle re-authentication.clearIdentityOnExpiry={false}
on the InternetIdentityProvider
. Consider your app's security requirements.See the CHANGELOG for details on updates.
Contributions are welcome. Please submit your pull requests or open issues to propose changes or report bugs.
This project is licensed under the MIT License. See the LICENSE file for more details.
FAQs
Hook that makes it easy to integrate IC Internet Identity into your React application.
The npm package ic-use-internet-identity receives a total of 394 weekly downloads. As such, ic-use-internet-identity popularity was classified as not popular.
We found that ic-use-internet-identity 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.
Research
/Security News
Socket researchers uncover how threat actors weaponize Discord across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
Security News
Socket now integrates with Bun 1.3’s Security Scanner API to block risky packages at install time and enforce your organization’s policies in local dev and CI.
Research
The Socket Threat Research Team is tracking weekly intrusions into the npm registry that follow a repeatable adversarial playbook used by North Korean state-sponsored actors.