Okta React SDK makes it easy to integrate react-router with Okta's OpenID Connect API.
This library currently supports:
- If you do not already have a Developer Edition Account, you can create one at https://developer.okta.com/signup/.
- If you don't have a React app, or are new to React, please continue with the React Quickstart guide. It will walk you through the creation of a React app, creating routes, and other application development essentials.
In Okta, applications are OpenID Connect clients that can use Okta Authorization servers to authenticate users. Your Okta Org already has a default authorization server, so you just need to create an OIDC client that will use it.
- Log into the Okta Developer Dashboard, click Applications then Add Application.
- Choose Single Page App (SPA) as the platform, then submit the form the default values, which should look like this:
Setting | Value |
---|---|
App Name | My SPA App |
Base URIs | http://localhost:{port} |
Login redirect URIs | http://localhost:{port}/implicit/callback |
Grant Types Allowed | Implicit |
After you have created the application there are two more values you will need to gather:
Setting | Where to Find |
---|---|
Client ID | In the applications list, or on the "General" tab of a specific application. |
Org URL | On the home screen of the developer dashboard, in the upper right. |
These values will be used in your React application to setup the OpenID Connect flow with Okta.
This library is available through npm. To install it, simply add it to your project:
npm install --save @okta/okta-react
okta-react
works directly with react-router
and provides four additional components:
- Security - (required) Allows you to supply your OpenID Connect client configuration.
- SecureRoute - (required) A normal
Route
except authentication is needed to render the component. - Callback - (required) Handles the implicit flow callback. This will parse the tokens and store them automatically.
Here are the minimum requirements for a working example:
- / - Anyone can access the home page
- /protected - Protected is only visible to authenticated users
- /implicit/callback - This is where auth is handled for you after redirection
// src/App.js
import React, { Component } from 'react';
import { BrowserRouter as Router, Route } from 'react-router-dom';
import { Security, SecureRoute, ImplicitCallback } from '@okta/okta-react';
import Home from './Home';
import Protected from './Protected';
class App extends Component {
render() {
return (
<Router>
<Security issuer='https://{yourOktaDomain}.com/oauth2/default'
client_id='{clientId}'
redirect_uri={window.location.origin + '/implicit/callback'} >
<Route path='/' exact={true} component={Home}/>
<SecureRoute path='/protected' component={Protected}/>
<Route path='/implicit/callback' component={ImplicitCallback} />
</Security>
</Router>
);
}
}
export default App;
In the relevant location in your application, you will want to provide Login
and Logout
buttons for the user. You can show/hide the correct button by using the auth.isAuthenticated()
method. For example:
// src/Home.js
import React, { Component } from 'react';
import { withAuth } from '@okta/okta-react';
export default withAuth(class Home extends Component {
constructor(props) {
super(props);
this.state = { authenticated: null };
this.checkAuthentication = this.checkAuthentication.bind(this);
this.checkAuthentication();
}
async checkAuthentication() {
const authenticated = await this.props.auth.isAuthenticated();
if (authenticated !== this.state.authenticated) {
this.setState({ authenticated });
}
}
componentDidUpdate() {
this.checkAuthentication();
}
render() {
if (this.state.authenticated === null) return null;
return this.state.authenticated ?
<button onClick={this.props.auth.logout}>Logout</button> :
<button onClick={this.props.auth.login}>Login</button>;
}
});
When your users are authenticated, your React application has an access token that was issued by your Okta Authorization server. You can use this token to authenticate requests for resources on your server or API. As a hypothetical example, let's say you have an API that provides messages for a user. You could create a MessageList
component that gets the access token and uses it to make an authenticated request to your server.
Here is what the React component could look like for this hypothetical example:
import fetch from 'isomorphic-fetch';
import React, { Component } from 'react';
import { withAuth } from '@okta/okta-react';
export default withAuth(class MessageList extends Component {
constructor(props) {
super(props)
this.state = {
messages: null
}
}
async componentDidMount() {
try {
const response = await fetch('http://localhost:{serverPort}/api/messages', {
headers: {
Authorization: 'Bearer ' + await this.props.auth.getAccessToken()
}
});
const data = await response.json();
this.setState({ messages: data.messages });
} catch (err) {
// handle error as needed
}
}
render() {
if (!this.state.messages) return <div>Loading..</div>;
const items = this.state.messages.map(message =>
<li key={message}>{message}</li>
);
return <ul>{items}</ul>;
}
});
Security is the top-most component of okta-react. This is where most of the configuration is provided.
-
issuer (required) - The OpenId Connect
issuer
-
client_id (required) - The OpenId Connect
client_id
-
redirect_uri (required) - Where the callback handler is hosted
-
onAuthRequired (optional)
-
auth (optional) - Provide an Auth object instead of the options above. This is helpful when integrating
okta-react
with external libraries that need access to the tokens.Accepts a callback to make a decision when authentication is required. If this is not supplied,
okta-react
redirects to Okta. This callback will receiveauth
andhistory
parameters. This is triggered when:auth.login
is called- SecureRoute is accessed without authentication
function customAuthHandler({auth, history}) {
// Redirect to the /login page that has a CustomLoginComponent
history.push('/login');
}
class App extends Component {
render() {
return (
<Router>
<Security issuer='https://{yourOktaDomain}.com/oauth2/default'
client_id='{clientId}'
redirect_uri={window.location.origin + '/implicit/callback'}
onAuthRequired={customAuthHandler} >
<Router path='/login' component={CustomLoginComponent}>
{/* some routes here */}
</Security>
</Router>
);
}
}
// src/App.js
import React, { Component } from 'react';
import { Router, Route } from 'react-router-dom';
import { Security, SecureRoute, ImplicitCallback, Auth } from '@okta/okta-react';
import Home from './Home';
import Protected from './Protected';
import { createBrowserHistory } from 'history'
const history = createBrowserHistory();
const auth = new Auth({
history,
issuer: 'https://{yourOktaDomain}.com/oauth2/default',
client_id: '{clientId}',
redirect_uri: window.location.origin + '/implicit/callback',
onAuthRequired: ({history}) => history.push('/login')
});
class App extends Component {
render() {
return (
<Router history={history}>
<Security auth={auth} >
<Route path='/' exact={true} component={Home}/>
<SecureRoute path='/protected' component={Protected}/>
<Route path='/implicit/callback' component={ImplicitCallback} />
</Security>
</Router>
);
}
}
export default App;
SecureRoute
ensures that a route is only rendered if the user is authenticated. If the user is not authenticated, it calls onAuthRequired
if it exists, otherwise, it redirects to Okta.
ImplicitCallback
handles the callback after the redirect. By default, it parses the tokens from the uri, stores them, then redirects to /
. If a SecureRoute
caused the redirect, then the callback redirects to the secured route.
withAuth
provides a way for components to make decisions based on auth state. It injects an auth
prop into the component.
auth
provides methods that allow managing tokens and auth state. All of the methods return Promises.
-
auth.isAuthenticated()
Returns
true
orfalse
, depending on whether the user has an active access or id token. -
auth.getUser()
Returns the result of the userinfo endpoint if an access token exists.
-
auth.getIdToken()
Retrieves the id token from storage if it exists.
-
auth.getAccessToken()
Retrieves the access token from storage if it exists.
-
auth.login()
Calls
onAuthRequired
or redirects to Okta ifonAuthRequired
is undefined. -
auth.logout()
Removes all the tokens and redirects to
/
. -
auth.redirect({sessionToken})
Performs a redirect to Okta with an optional
sessionToken
.Example:
auth.redirect({ sessionToken: '{sampleSessionToken}' });
-
auth.handleAuthentication()
Parses tokens from the url and stores them.
- Clone the repo:
git clone [email protected]:okta/okta-oidc-js.git
- Install the dependencies with lerna (install with
npm i lerna -g
):
lerna bootstrap
- Navigate into the
okta-react
package:
cd packages/okta-react
- Make your changes to
okta-react/src/
- Set the following environment variables:
ISSUER
- your authorization serverCLIENT_ID
- the client id of your app
- Start a sample server:
npm start
Command | Description |
---|---|
npm start |
Start the sample app using the SDK |
npm test |
Run integration tests |
npm run lint |
Run eslint linting tests |