Commit Graph

14 Commits

Author SHA1 Message Date
e333d07c14 feat(hydra-dispatcher): maj ref image hydra-dispatcher pour ajout url_link env var 2023-12-13 10:41:44 +01:00
435597f9f1 feat(hydra-dispatcher): update image tag 2023-12-11 10:47:56 +01:00
ee2bb1ea45 update hydra-dispatcher probes and image ref 2023-12-11 10:47:56 +01:00
63c5d7259c add probes 2023-12-11 10:47:56 +01:00
5ec48c8b22 update config default apps filename 2023-12-11 10:47:56 +01:00
8c6dc30bde set hydra-dispatcher side container 2023-12-11 10:47:56 +01:00
4ff0f83880 set hydra-dispatcher side container 2023-12-11 10:47:56 +01:00
e93bc069d3 set correct path for hydra-dispatcher conf 2023-12-11 10:47:56 +01:00
a56089efe5 Utilisation images symfony-containers 2023-12-11 10:47:56 +01:00
8fe8423071 fix: example app deployment with saml login app 2023-11-07 10:29:45 +01:00
8075071f22 feat(resource): adding new hydra-maester resource
This allow to manage "Clients" with a CRD

from official doc:

The controller listens for Custom Resource which defines client registration request.
Once Custom resource is created, the controller register oauth2 client in hydra using
hydra's REST API.

Client Id, Client Secret and Identifier of the client in hydra are be stored in the
kubernetes as a secret and referenced in the applied CR. Reference is used to
identify in which kubernetes secret are stored mentioned properties.

Secret iscreated in the same namespace of applied CR. By default controller should
be deployed in the same pod as hydra. Service discovery will come in place in the future.
2023-06-12 14:07:51 +02:00
4a745fb9a1 wip: example app 2023-02-27 09:36:36 +01:00
51535d76bf feat(hydra-dispatcher): mount default apps config as volume 2023-02-01 11:30:41 +01:00
06b7aa7903 feat: initial commit 2023-01-27 10:16:19 +01:00