headscale/integration
Kristoffer Dalby da48cf64b3 Set OpenID Connect Expiry
This commit adds a default OpenID Connect expiry to 180d to align with
Tailscale SaaS (previously infinite or based on token expiry).

In addition, it adds an option use the expiry time from the Token sent
by the OpenID provider. This will typically cause really short expiry
and you should only turn on this option if you know what you are
desiring.

This fixes #1176.

Co-authored-by: Even Holthe <even.holthe@bekk.no>
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
2023-01-31 18:55:16 +01:00
..
dockertestutil Improve generated integration tests 2023-01-30 14:43:03 +01:00
hsic Improve generated integration tests 2023-01-30 14:43:03 +01:00
integrationutil Remove some very verbose error outputs 2022-11-21 14:37:50 +01:00
tsic Add logout method to tsic 2022-12-22 00:09:21 +01:00
auth_oidc_test.go Set OpenID Connect Expiry 2023-01-31 18:55:16 +01:00
auth_web_flow_test.go modify the test to reflect the changes on the webinterface 2023-01-26 08:33:44 +01:00
cli_test.go Improve generated integration tests 2023-01-30 14:43:03 +01:00
control.go Improve generated integration tests 2023-01-30 14:43:03 +01:00
general_test.go Rename [Nn]amespace -> [Uu]ser in go code 2023-01-18 15:40:04 +01:00
README.md Add integration readme 2023-01-06 12:32:24 +01:00
scenario_test.go Rename [Nn]amespace -> [Uu]ser in go code 2023-01-18 15:40:04 +01:00
scenario.go Improve generated integration tests 2023-01-30 14:43:03 +01:00
ssh_test.go Rename [Nn]amespace -> [Uu]ser in go code 2023-01-18 15:40:04 +01:00
tailscale.go Add logout method to tsic 2022-12-22 00:09:21 +01:00

Integration testing

Headscale relies on integration testing to ensure we remain compatible with Tailscale.

This is typically performed by starting a Headscale server and running a test "scenario" with an array of Tailscale clients and versions.

Headscale's test framework and the current set of scenarios are defined in this directory.

Tests are located in files ending with _test.go and the framework are located in the rest.

Running integration tests on GitHub Actions

Each test currently runs as a separate workflows in GitHub actions, to add new test, add the new test to the list in ../cmd/gh-action-integration-generator/main.go and run go generate inside ../cmd/gh-action-integration-generator/ and commit the result.