Cover self-vetting of a GSSP token in behat test scenario

[phavekes]

This issue is imported from pivotal - Originaly created at Apr 16, 2024 by Michiel Kodde

We recently ran into a bug where the GSSP ACS action was unable to route to the self vet controller. That issue could have been spotted if we covered this scenario in a behat test.

Suggestion: Add a self-vet registration of a gssp token to the global behat test suite

[MKodde]

The existing tests can be found here:

https://github.com/OpenConext/OpenConext-devconf/blob/63ca75d72b8b8258011295fc241a1260d34b1dd2/stepup/tests/behat/features/self_vet.feature

The step definitions allow for interaction with the demo-gssp token. So you should be able to use that token for the new self vet gssp test. @pablothedude seems to have added some of this test coverage in 2025-04-16. So maybe a verification if that test coverage is ample will suffice here..

https://github.com/OpenConext/OpenConext-devconf/blob/63ca75d72b8b8258011295fc241a1260d34b1dd2/stepup/tests/behat/features/self_vet.feature#L53-L62

[johanib]

@johanib Check tests then ticket complete.

[MKodde]

@phavekes I think that exact scenario is covered in the test that Bas added a couple of months ago. I think this can be closed. Do you agree?