## Documentation

- About
- Read First
  - What is IdentityServer
  - Installation Scenarios
- Migrations
- Configuration & Integration
  - Configuring AdminUI
  - Integrating with Identity Server
  - Integrating with Quickstarts
  - Enabling Logging
- Installation
  - IIS
  - Azure
  - Docker
  - Installer
- Users
  - Users
  - Searching for Users
  - Adding Users
  - Editing Users
  - User Roles
  - User Claims
  - User Applications
  - Deleting Users
- Roles
  - Roles
  - Searching for Roles
  - Creating Roles
  - Users In Role
  - Editing Roles
  - Deleting Roles
  - Role Management
- Claim Types
  - Searching for Claims
  - Creating Claims
  - Editing Claims
  - Deleting Claims
- Clients
  - Clients
  - Searching for Clients
  - Adding Clients
  - Adding a SPA Client
  - Adding a Web Client
  - Adding a Robot Client
  - Adding a SAML Client
  - Adding a WS-Fed Client
  - Editing Clients
  - Deleting Clients
  - Exporting Clients
- Resources
  - Resources
  - Searching for Resources
  - Creating Resources
  - Editing resources
  - Disabling Resources
- Webhooks
  - Webhooks
  - User Registration Endpoint
  - Password Reset Endpoint
- User Settings Endpoints
  - Authorisation
  - Endpoints
- Access Policy
  - Access Policy
  - Permissions
  - Managing your Access Policy
- Audit
  - View Audit Events
  - IdentityServer Auditing
  - Auditing Database
  - Audit Language

### Adding a SPA Client

- -Adding a Single Page Application
- -SPA Callback Url
- -SPA Logout Url
- -SPA Identity Resources
- -SPA Protected Resources
- -SPA Details Review
- -Back
- -Success
- -HTTPS

## Adding a Single Page Application

From the Add a Client workflow, if you choose to setup a Single Page application, you will see a dialogue enabling you to add the following:

- `Client ID` Unique identifier
- `Display Name` Application name that will be seen on Consent Screens
- `Display URL` Application URL that will be seen on Consent Screens
- `Logo URL` Application Logo that will be seen on Consent Screens. Note - must be HTTPS
- `Description` Application description for use within AdminUI

Click next once all details have been filled in as required:

### SPA Callback Url

You will be asked to enter a Callback URL, which is the endpoint where tokens will be sent to. This can be configured more after setup, and is the full path of the redirect URL. This must be over HTTPS:

### SPA Logout Url

You will next be asked to enter a Post-Logout URL. This is optional and you can configure more after setup - it is where users can be returned to after logging out. This must be HTTPS:

### SPA Identity Resources

You will next be asked to select the Identity Resources that this client can access:

### SPA Protected Resources

At this point, you can now choose the Protected Resources that this client can access:

### SPA Details Review

You will get the chance to finally review all details at the end of the application process, when you will see a summary of all details entered so far.

To edit, click the pencil icon and you will be returned to the page to amend those details. For instance, editing the Display Name will return you to the Basic Details

### Back

If at any point after entering the basic details you wish to go back, you can navigate backwards and forwards within the application using the links at the foot of the modal, or cancel out of the entire process:

### Success

Once clicking submit, you will have successfully added a SPA Client.

### HTTPS

If the `Logo URL`, the application Logo that will be seen on Consent Screens, is not HTTPS, then it will not display.

The `Callback URL` and `Logout URL` must also be HTTPS.

Previous Next