
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
keycloak-react-web
Advanced tools
Keycloak React Web has been built on top of keycloak-js extending all of its functionalities to provide a global authentication support for your react applications.
Keycloak React Web has been built on top of keycloak-js extending all of its functionalities to provide a global authentication support for your react applications.
Using npm :
npm i keycloak-react-web
Wrap your application inside the given provider.
import { KeycloakProvider } from "keycloak-react-web";
<KeycloakProvider client={authInstance} initOptions={{initOptions}}>
<YOUR APP CODE GOES HERE>
</KeycloakProvider>
Here "authInstance" is a Keycloak instance having proper configuration of realm, clientIds, urls of keycloak and can be initialized like:
const authInstance = new Keycloak(keycloakSetting)
where
const keycloakSetting = {
url: <keycloak base url>,
realm: <keycloak realm name>,
clientId: <keycloak client id>
};
initOptions: <optional>
This is an optional field. Refer option parameter of init function https://www.keycloak.org/docs/latest/securing_apps/index.html#methods
You can use provided custom hook to check the authentication status for all your private routes/components as:
import { useKeycloak } from "keycloak-react-web";
const { keycloak, initialized } = useKeycloak();
check if user is authenticated or not:
const authenticated = keycloak.authenticated
Getting tokens
const token = keycloak.token;
const refreshToken = keycloak.refreshToken;
refer https://www.keycloak.org/docs/latest/securing_apps/index.html#_javascript_adapter for all available properties present on keycloak instance.
Expample shows private route which will be accessible to authenticated users
import React from 'react';
import { BrowserRouter as Router, Routes, Route } from 'react-router-dom';
import { KeycloakProvider, useKeycloak } from "keycloak-react-web"
import Keycloak from 'keycloak-js';
const keycloakSetting = {
url: <keycloak base url>,
realm: <keycloak realm name>,
clientId: <keycloak client id>
};
const authInstance = new Keycloak(keycloakSetting)
function App() {
return (
<KeycloakProvider client={authInstance}>
<Router>
<Routes>
<Route
path={'/'}
element={<PrivateRoute component={Component} />}
/>
</Routes>
</Router>
</KeycloakProvider>
);
}
const PrivateRoute = ({ component: Component }) => {
const { keycloak, initialized } = useKeycloak();
const context = useContext(UserContext);
useEffect(() => {
if (initialized) {
if (!keycloak.authenticated) {
keycloak.login();
}
}
}, [initialized]);
if (!initialized) {
return <p>Loading...</p>;
}
if (!keycloak.authenticated) {
return <p>Authenticating...</p>;
}
return (
<Component />
);
};
FAQs
Keycloak React Web has been built on top of keycloak-js extending all of its functionalities to provide a global authentication support for your react applications.
The npm package keycloak-react-web receives a total of 398 weekly downloads. As such, keycloak-react-web popularity was classified as not popular.
We found that keycloak-react-web demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.