Project: Keycloak (Provisioning / Security & Compliance)
File: tests.md

Executing tests =============== Running the tests -- It is recommended to take a look at . Browser The testsuite uses Selenium. By default it uses the HtmlUnit WebDriver, but can also be executed with Chrome or Firefox. To run the tests with Firefox add `-Dbrowser=firefox` or for Chrome add `-Dbrowser=chrome` Database -- By default the testsuite uses an embedded H2 database to test with other databases see . Test utils ========== All the utils can be executed from the directory testsuite/utils: cd testsuite/utils Keycloak server To start a basic Keycloak server for testing run: mvn exec:java -Pkeycloak-server or run org.keycloak.testsuite.KeycloakServer from your favourite IDE! When starting the server it can also import a realm from a json file: mvn exec:java -Pkeycloak-server -Dimport=testrealm.json When starting the server, https transport can be set up by setting keystore containing the server certificate and https port, optionally setting the truststore. mvn exec:java -Pkeycloak-server \ -Djavax.net.ssl.trustStore=/path/to/truststore.jks \ -Djavax.net.ssl.keyStore=/path/to/keystore.jks \ -Djavax.net.ssl.keyStorePassword=CHANGEME \ -Dkeycloak.port.https=8443 KeycloakServer can be configured with system properties, or through the file `~/.keycloak-server.properties`. Using the file allows persisting the settings and can also be more convenient when running from an IDE. Available options include: |Key| Description | ||| |keycloak.port| Set the HTTP port for the server | |keycloak.port.https| Set the HTTPS port for the server | |keycloak.bind.address| Set the bind address for the server | |resources| Loads theme resources directly from the workspace and disables caching | |keycloak.theme.dir| Specifies an alternative location to load custom themes from | |keycloak.theme.cacheTemplates| Disables theme template caching | |keycloak.theme.cacheThemes| Disables theme caching | |keycloak.theme.staticMaxAge| Sets the client-side caching max-age for theme resources | |import| Imports a realm from json at startup | The default admin within the master realm are created with credentials: Username: `admin` Password: `admin` The Keycloak test suite server will automatically create the new master realm user when the following conditions are met Property `keycloak.createAdminUser` is set to `true` (defaults to `true` if not present) There is no existing user within the master realm The Keycloak test server can load resources directly from the filesystem instead of the classpath. This allows editing html, styles and updating images without restarting the server. To make the server use resources from the filesystem start with: mvn exec:java -Pkeycloak-server -Dresources You can also specify the theme directory used by the server with: mvn exec:java -Pkeycloak-server -Dkeycloak.theme.dir=<PATH TO THEMES DIR> For example to use the example themes run the server with: mvn exec:java -Pkeycloak-server -Dkeycloak.theme.dir=examples/themes NOTE: If `keycloak.theme.dir` is specified the default themes (base, rcue and keycloak) are loaded from the classpath TOTP codes To generate totp codes without Google authenticator run: mvn exec:java -Ptotp or run org.keycloak.testsuite.TotpGenerator from your favourite IDE! Once started copy/paste the totp secret and press enter. To use a new secret just copy/paste and press enter again. Mail server -- To start a test mail server for testing email sending run: mvn exec:java -Pmail-server or run org.keycloak.testsuite.MailServer from your favourite IDE! To configure Keycloak to use the above server add the following system properties: keycloak.mail.smtp.from=auto@keycloak.org keycloak.mail.smtp.host=localhost keycloak.mail.smtp.port=3025 For example if using the test utils Keycloak server start it with: mvn exec:java -Pkeycloak-server -Dkeycloak.mail.smtp.from=auto@keycloak.org -Dkeycloak.mail.smtp.host=localhost -Dkeycloak.mail.smtp.port=3025 LDAP server -- To start a ApacheDS based LDAP server for testing LDAP sending run: mvn exec:java -Pldap There are additional system properties you can use to configure (See LDAPEmbeddedServer class for

Once done, you can create LDAP Federation provider in Keycloak admin console with the settings like: Vendor: Other Connection URL: ldap://localhost:10389 User DN Suffix: ou=People,dc=keycloak,dc=org Bind DN: uid=admin,ou=system Bind credential: secret Kerberos server To start a ApacheDS based Kerberos server for testing Kerberos + LDAP sending run: mvn exec:java -Pkerberos There are additional system properties you can use to configure (See LDAPEmbeddedServer and KerberosEmbeddedServer class for details) but for testing purposes default values should be good. By default ApacheDS LDAP server will be running on localhost:10389 and Kerberos KDC on localhost:6088 . The alternative is to start Kerberos with the alternative realm KC2.COM instead of default KEYCLOAK.ORG. The ApacheDS server will be then started with all ports shifted by 1000 (EG. LDAP on 11389, Kerberos KDC on 7088). This allows to start 2 kerberos servers in parallel to test things like Kerberos cross-realm trust: mvn exec:java -Pkerberos -Dkeycloak.kerberos.realm=KC2.COM Once kerberos is running, you can create LDAP Federation provider in Keycloak admin console with same settings like mentioned in previous LDAP section. But additionally you can enable Kerberos authentication in LDAP provider with the settings like: Kerberos realm: KEYCLOAK.ORG Server Principal: HTTP/localhost@KEYCLOAK.ORG KeyTab: $KEYCLOAKSOURCES/testsuite/integration-arquillian/tests/base/src/test/resources/kerberos/http.keytab (Replace $KEYCLOAKSOURCES with correct absolute path of your sources) Once you do this, you should also ensure that your Kerberos client configuration file is properly configured with KEYCLOAK.ORG domain. See for inspiration. The location of Kerberos configuration file is platform dependent (In linux it's file `/etc/krb5.conf` ) Then you need to configure your browser to allow SPNEGO/Kerberos login from `localhost` . Exact steps are again browser dependent. For Firefox see for example . URI `localhost` must be allowed in `network.negotiate-auth.trusted-uris` config option. For Chrome, you just need to run the browser with command similar to this (more details in Chrome documentation): ``` /usr/bin/google-chrome-stable --auth-server-whitelist="localhost" ``` Finally test the integration by retrieve kerberos ticket. In many OS you can achieve this by running command from CMD like: ``` kinit hnelson@KEYCLOAK.ORG ``` and provide password `secret` Now when you access `http://localhost:8081/auth/realms/master/account` you should be logged in automatically as user `hnelson` . Simple loadbalancer You can run class `SimpleUndertowLoadBalancer` from IDE. By default, it executes the embedded undertow loadbalancer running on `http://localhost:8180`, which communicates with 2 backend Keycloak nodes running on `http://localhost:8181` and `http://localhost:8182` . See javadoc for more details. Create many users or offline sessions Run testsuite with the command like this: ``` mvn exec:java -Pkeycloak-server -DstartTestsuiteCLI ``` Alternatively if you want to use your MySQL database use the command like this (replace properties values according your DB connection): ``` mvn exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url=jdbc:mysql://localhost/keycloak -Dkeycloak.connectionsJpa.driver=com.mysql.jdbc.Driver -Dkeycloak.connectionsJpa.user=keycloak -Dkeycloak.connectionsJpa.password=keycloak -DstartTestsuiteCLI ``` Then once CLI is started, you can use command `help` to see all the available commands. For create many users you can use command `createUsers` For example this will create 500 users `test0, test1, test2, ... , test499` in realm `demo` and each 100 users in separate transaction. All users will be granted realm roles `user` and `admin` : ``` createUsers test test demo 0 500 100 user,admin ``` Check count of users: ``` getUsersCount demo ``` Check if concrete user was really created: ``` getUser demo test499 ``` For create many offline sessions you can use command `persistSessions` . For example create 50000 sessions (each 500 in separate transaction) with command: ``` persistSessions 50000 500 ``` Once users or sessions are created, you can restart to ensure the startup import of offline sessions will be triggered and you can see impact on startup time. After restart you can use command: ``` size ``` to doublecheck total count of sessions in infinispan (it will be 2 times as there is