Commits on Source (3)
-
Ryan Gonzalez authored
Technically this is supposed to be the default method in the first place, and it's what qa-report-app uses. https://phabricator.apertis.org/T10554 Signed-off-by:
Ryan Gonzalez <ryan.gonzalez@collabora.com>
68d071d6 -
Ryan Gonzalez authored
Useful for testing purposes. Signed-off-by:
Ryan Gonzalez <ryan.gonzalez@collabora.com>
78bbce17 -
With commit ad28b94f "Validate client_id and client_secret values" the mediator started paying attention to client authentication. Since our integration test cargo-culted some configuration parameter straight from the GitLab configuration examples the mediator ended up implementing what the OpenID-Connect spec calls the `client_secret_post` authentication method, see https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication Unfortunately, the spec also says that the actual default is `client_secret_basic`, so any real world usage is bound to fail unless some specific configuration is applied. To minimize confusion, let's drop the cargo-culted option from the example and add a note pointing to the spec and to the upstream GitLab documentation, while still keeping the `client_secret_post` usage in the GitLab integration test to exercise the codepath. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
f572b8af
Showing
- README.md 15 additions, 1 deletionREADME.md
- docker-compose-gitlab.yaml 2 additions, 0 deletionsdocker-compose-gitlab.yaml
- docker-compose-qa.yaml 72 additions, 0 deletionsdocker-compose-qa.yaml
- mediator/handlers.go 13 additions, 9 deletionsmediator/handlers.go
- mediator/mediator_test.go 92 additions, 42 deletionsmediator/mediator_test.go
- qa-config.yaml 18 additions, 0 deletionsqa-config.yaml
docker-compose-qa.yaml
0 → 100644
qa-config.yaml
0 → 100644