devproje/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2024-11-26 08:53:05 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
headscale/integration
History
Kristoffer Dalby 218138afee
Redo OIDC configuration (#2020) 
expand user, add claims to user

This commit expands the user table with additional fields that
can be retrieved from OIDC providers (and other places) and
uses this data in various tailscale response objects if it is
available.

This is the beginning of implementing
https://docs.google.com/document/d/1X85PMxIaVWDF6T_UPji3OeeUqVBcGj_uHRM5CI-AwlY/edit
trying to make OIDC more coherant and maintainable in addition
to giving the user a better experience and integration with a
provider.

remove usernames in magic dns, normalisation of emails

this commit removes the option to have usernames as part of MagicDNS
domains and headscale will now align with Tailscale, where there is a
root domain, and the machine name.

In addition, the various normalisation functions for dns names has been
made lighter not caring about username and special character that wont
occur.

Email are no longer normalised as part of the policy processing.

untagle oidc and regcache, use typed cache

This commits stops reusing the registration cache for oidc
purposes and switches the cache to be types and not use any
allowing the removal of a bunch of casting.

try to make reauth/register branches clearer in oidc

Currently there was a function that did a bunch of stuff,
finding the machine key, trying to find the node, reauthing
the node, returning some status, and it was called validate
which was very confusing.

This commit tries to split this into what to do if the node
exists, if it needs to register etc.

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
2024-10-02 14:50:17 +02:00
..
dockertestutil Add compatibility with only websocket-capable clients (#2132) 2024-09-21 12:05:36 +02:00
hsic use gorm serialiser instead of custom hooks (#2156) 2024-10-02 11:41:58 +02:00
integrationutil Add go profiling flag, and enable on integration tests (#1382) 2023-04-27 16:57:11 +02:00
tsic Add compatibility with only websocket-capable clients (#2132) 2024-09-21 12:05:36 +02:00
acl_test.go add shutdown that asserts if headscale had panics (#2126) 2024-09-17 11:44:55 +02:00
auth_oidc_test.go Redo OIDC configuration (#2020) 2024-10-02 14:50:17 +02:00
auth_web_flow_test.go add shutdown that asserts if headscale had panics (#2126) 2024-09-17 11:44:55 +02:00
cli_test.go add shutdown that asserts if headscale had panics (#2126) 2024-09-17 11:44:55 +02:00
control.go make stream shutdown if self-node has been removed (#2125) 2024-09-11 12:00:32 +02:00
dns_test.go Add compatibility with only websocket-capable clients (#2132) 2024-09-21 12:05:36 +02:00
embedded_derp_test.go Add compatibility with only websocket-capable clients (#2132) 2024-09-21 12:05:36 +02:00
general_test.go add shutdown that asserts if headscale had panics (#2126) 2024-09-17 11:44:55 +02:00
README.md Add section about running locally 2023-02-03 16:25:58 +01:00
route_test.go add shutdown that asserts if headscale had panics (#2126) 2024-09-17 11:44:55 +02:00
run.sh Fix 764 (#2093) 2024-09-03 09:22:17 +02:00
scenario.go remove versions older than 1.56 (#2149) 2024-09-24 18:34:20 +02:00
scenario_test.go add shutdown that asserts if headscale had panics (#2126) 2024-09-17 11:44:55 +02:00
ssh_test.go add shutdown that asserts if headscale had panics (#2126) 2024-09-17 11:44:55 +02:00
tailscale.go Add compatibility with only websocket-capable clients (#2132) 2024-09-21 12:05:36 +02:00
utils.go Add compatibility with only websocket-capable clients (#2132) 2024-09-21 12:05:36 +02:00

README.md

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 locally

The easiest way to run tests locally is to use [act](INSERT LINK), a local GitHub Actions runner:

act pull_request -W .github/workflows/test-integration-v2-TestPingAllByIP.yaml

Alternatively, the docker run command in each GitHub workflow file can be used.

Running integration tests on GitHub Actions

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