Supporting resources for deployment of SPA code examples which use the Token Handler Pattern.
The OAuth Agent manages OpenID Connect work for the SPA and issues secure cookies to use in the browser:
The token handler pattern requires additional supporting components to be deployed:
Deployment on development computer involves the following main steps:
| Step | Description |
|---|---|
| Prerequisites | Ensuring that the correct prerequisite tools are installed |
| Build Code | Building code and dependencies into Docker images |
| Configure SSL Trust | Ensuring that development certificates are trusted by the system |
| Deploy the System | Deploying the Curity Identity Server and other supporting components |
| Run the SPA | Browsing to the SPA and signing in as the preconfigured user account |
Start with the main SPA repository, and follow the instructions in these pages:
- Standard SPA using an Authorization Code Flow (PKCE) and a Client Secret
- Financial-grade SPA using Mutual TLS, PAR and JARM
See the following repositories for further details on how to work with an OAuth Agent:
Please visit curity.io for more information about the Curity Identity Server.