Skip to content
Branch: master
Find file History
Latest commit 3fdd20a Aug 29, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
public Iterate samples to V2 spec (#13) Jan 6, 2018
src Use PKCE flow Aug 30, 2019
.gitignore Iterate samples to V2 spec (#13) Jan 6, 2018
README.md Use PKCE flow Aug 30, 2019
config-overrides.js Use PKCE flow Aug 30, 2019
package-lock.json Use PKCE flow Aug 30, 2019
package.json Use PKCE flow Aug 30, 2019

README.md

Okta React + Custom Login Example

This example shows you how to use the Okta React Library to login a user to a React application. The login is achieved with the Okta Sign In Widget, which gives you more control to customize the login experience within your app.

This example is built with Create React App.

Prerequisites

Before running this sample, you will need the following:

  • An Okta Developer Account, you can sign up for one at https://developer.okta.com/signup/.
  • An Okta Application, configured for Singe-Page App (SPA) mode. This is done from the Okta Developer Console and you can find instructions here. When following the wizard, use the default properties. They are are designed to work with our sample applications.

Running This Example

To run this application, you first need to clone this repo and then enter into this directory:

git clone https://github.com/okta/samples-js-react.git
cd samples-js-react/custom-login

Then install dependencies:

npm install

Now you need to gather the following information from the Okta Developer Console:

  • Client Id - The client ID of the SPA application that you created earlier. This can be found on the "General" tab of an application, or the list of applications. This identifies the application that tokens will be minted for.
  • Issuer - This is the URL of the authorization server that will perform authentication. All Developer Accounts have a "default" authorization server. The issuer is a combination of your Org URL (found in the upper right of the console home page) and /oauth2/default. For example, https://dev-1234.oktapreview.com/oauth2/default.

These values must exist as environment variables. They can be exported in the shell, or saved in a file named testenv, at the root of this repository. (This is the parent directory, relative to this README) See dotenv for more details on this file format.

ISSUER=https://yourOktaDomain.com/oauth2/default
CLIENT_ID=123xxxxx123

With variables set, start the app server:

npm start

Now navigate to http://localhost:8080 in your browser.

If you see a home page that prompts you to login, then things are working! Clicking the Log in button will render a custom login page component that uses the Okta Sign-In Widget to perform authentication.

You can login with the same account that you created when signing up for your Developer Org, or you can use a known username and password from your Okta Directory.

Note: If you are currently using your Developer Console, you already have a Single Sign-On (SSO) session for your Org. You will be automatically logged into your application as the same user that is using the Developer Console. You may want to use an incognito tab to test the flow from a blank slate.

Integrating The Resource Server

This sample contains the same "Messages" page that is included in the Okta Hosted Login sample, please refer to that sample for instructions on setting up the resource server.

You can’t perform that action at this time.