Testing your environment
By this point, you should have a local environment very close to what will become your production environment.
In the previous topics in this chapter, we have covered the following:
- Setting up Keycloak to use a public domain name for frontend and backend endpoints, as well as logically grouping the different Keycloak instances under a single issuer
- Setting up Keycloak to listen on HTTPS so that all traffic to and from Keycloak is secure
- Setting up Keycloak to use a production-grade database using PostgreSQL
- Setting up clustering so that multiple instances of Keycloak can share the state kept by their caches
- Setting up a reverse proxy, using HAProxy, so that we can finally access all Keycloak instances through a single public domain name
In the following topics, you are going to perform some basic tests on the environment to make sure everything is working as expected.
Before we begin, make sure HAProxy is...
