---
title: Adding Clients
---

## Adding a Client

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

![Add Client](img/addclient.png)

### 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.

![Add Client](img/addclient2.png)

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:

![Set Up SPA](img/setupspanew.png)

### 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:

![Call Back URL](img/callbackurl.png)

### 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: 

![Post Log Out](img/postlogouturl.png)

### SPA Identity Resources

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

![SPA Identity](img/spaidentityresources1.png)

### SPA Protected Resources

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

![Protected Resources](img/protectedresources2.png)

### 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. 

![SPA edit](img/spaedit.png)

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:

![Back and Next](img/backnext.png)

### 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

![Secrets](img/secretstep.png)