libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases 1 Packages Activity Actions

Update HOW-TO-RUN.md

Browse source
This commit is contained in:
Stian Thorgersen 2021-04-15 10:50:33 +02:00 committed by Stian Thorgersen
parent 20b29f7b99
commit c868e1b173
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
testsuite/integration-arquillian/HOW-TO-RUN.md
View file

@ -499,6 +499,11 @@ mvn -f testsuite/integration-arquillian/tests/other/base-ui/pom.xml \
tests in the Base UI testsuite are executed please use `-DchromeArguments=--enable-web-authentication-testing-api` as tests in the Base UI testsuite are executed please use `-DchromeArguments=--enable-web-authentication-testing-api` as
specified in [WebAuthn tests](#webauthn-tests). specified in [WebAuthn tests](#webauthn-tests).
## Disabling features
Some features in Keycloak can be disabled. To run the testsuite with a specific feature disabled use the `auth.server.feature` system property. For example to run the tests with authorization disabled run:
```
mvn -f testsuite/integration-arquillian/tests/base/pom.xml clean test -Pauth-server-wildfly -Dauth.server.feature=-Dkeycloak.profile.feature.authorization=disabled
```
## WebAuthN tests ## WebAuthN tests
The WebAuthN tests, in Keycloak, can be only executed with Chrome browser, because the Chrome has feature _WebAuthenticationTestingApi_, The WebAuthN tests, in Keycloak, can be only executed with Chrome browser, because the Chrome has feature _WebAuthenticationTestingApi_,
which simulate hardware authentication device. For automated WebAuthN testing, this approach seems like the best choice so far. which simulate hardware authentication device. For automated WebAuthN testing, this approach seems like the best choice so far.