## Documentation

- About
- Read First
  - What is IdentityServer
  - Installation Scenarios
- Migrations
- Bootstrapping
- Configuration & Integration
  - AdminUI Settings
  - Configuring AdminUI
  - Configuring AdminUI (NuGet)
  - Integrating with Identity Server
  - Integrating with Identity Server Custom Schema
  - Integrating with Quickstarts
  - Enabling Logging
- Installation
  - Installer
  - IIS
  - Azure
    - Install in Azure
    - Create Azure Web App
  - Docker
  - NuGet
- Custom Database Connections
- Custom Identity Store
  - Overview
  - Partial Implementation
  - Full Implementation
  - Tenancy With Entity Framework
  - NoSql Implementation (MongoDB)
- Custom CSP
- Users
  - Searching for Users
  - Adding Users
  - Editing Users
  - Deleting Users
  - Merge Users
  - Set User Password
  - Session Management
  - User Reports
  - Bulk User Import
- Roles
  - Creating Roles
  - Managing Roles
  - Managing Users in a Role
  - Managing Role Claims
- Claim Types
- Clients
  - Searching for Clients
  - Adding Clients
  - Adding a SAML Client
  - Adding a WS-Fed Client
  - Editing Clients
  - Deleting Clients
  - Clone Client
- Import and Export
  - Exporting Clients
  - Importing Clients
  - Importing Client Configuration with Secrets
  - Importing SAML Clients with Certificates
  - Import and Export Via the API
- Dynamic Authentication Providers
  - What is Dynamic Authentication
  - Enabling or disabling Dynamic Authentication
  - Add a Dynamic Provider
    - First Steps
    - Adding OIDC Provider
    - Adding SAML Provider
  - Edit a Dynamic Provider
    - Accessing edit view
    - Editing a OIDC Provider
    - Editing a SAML Provider
  - Deleting a Provider
  - Searching for Provider
- Resources
  - Searching for Resources
  - Creating Resources
  - Editing resources
- Webhooks
  - Webhooks
  - Endpoint Configuration
- User Settings Endpoints
- Access Policy
- Keys
- Auditing
- FAQs
- Troubleshooting
  - Unable to start AdminUI
  - Unable to contact IdentityServer
  - Unable to contact API
  - Unable to log in

### Adding Clients

- -Adding a Client
- -Client Type
- -SPA Callback Url
- -SPA Logout Url
- -SPA Identity Resources
- -SPA Protected Resources
- -SPA Details Review
- -Back
- -Success
- -Secrets

## Adding a Client

From the Clients page, click the "Add Client" button

### Client Type

Choose the client type you require from the 8 available options:

1. `Single Page App` A client-side application running in a browser.
2. `Web App` A server-side application running on your infrastructure.
3. `Native` A desktop or mobile application running on a user's device.
4. `Machine` A machine-to-machine method of communication.
5. `Device` An IoT application or otherwise browserless or input constrained device.
6. `SAML Service Provider` A SAML 2.0 service provider commonly used by government and educational institutions.
7. `WS-Fed Relying Party` A WS-Federation relying party commonly used by older Microsoft applications.
8. `Single Page App (legacy)` A client-side application running in a browser using previous OAuth Working Group recommendations.

Proceed with the required Client and follow instructions for each client type.

For this example i will be setting up a Single Page application, many of these steps are relevant when setting up other client types.

After selecting the SPA options 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
- `Require Consent` Specifies whether a consent screen is required for this client

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.

### Secrets

For relevant clients, you will be asked to optionally add some secrets.

You can select a Secret Type of either a `Shared Secret` or an `X509 Certificate Thumbprint`.

Once you have filled out and entered the required Secret details, click "Add" and the Secret will be added to the client on creation

Previous Next