Commit Graph

8 Commits

Author SHA1 Message Date
380a116fa8 fix(all): use app.kubernetes.io/name label instead of io.kompose.service 2024-02-21 15:43:42 +01:00
fcfbb6cc30 correction port mapping de hydra-remote-user 2023-12-15 15:25:02 +01:00
dd6804aa11 feat(shibboleth-sp): update dev ref image 2023-12-13 09:38:05 +01:00
77eb73818f feat(hydra-remote-user): update dev image ref 2023-12-13 09:38:05 +01:00
bc6fe46e1c fix(saml): fixing port name longer than 15c 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
d2960e3be2 feat: add hydra-saml component 2023-02-01 16:34:33 +01:00