Commit Graph

14 Commits

Author SHA1 Message Date
wpetit 6de80b1d9c fix(hydra-ldap): update werther secret name references 2023-12-11 10:06:37 +01:00
wpetit 2f3cf60974 fix(hydra-ldap): update werther container port name 2023-12-11 09:56:27 +01:00
wpetit bf865b02e2 feat(hydra-ldap): rename resources from werther to hydra-ldap 2023-12-11 09:50:33 +01:00
Laurent Gourvenec 063b575117 feat(werther): update image 2023-12-06 15:38:40 +01:00
Laurent Gourvenec 38d3f1c1df feat(werther): adding a timeout for LDAP connection 2023-12-06 14:40:24 +01:00
Laurent Gourvenec 6acda0553e feat(component): adding werther 2023-11-29 10:22:33 +01:00
wpetit 8fe8423071 fix: example app deployment with saml login app 2023-11-07 10:29:45 +01:00
Philippe Caseiro 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
wpetit 4a745fb9a1 wip: example app 2023-02-27 09:36:36 +01:00
wpetit d2960e3be2 feat: add hydra-saml component 2023-02-01 16:34:33 +01:00
wpetit f93ae0b4ba feat(hydra-oidc): add default environment 2023-02-01 15:16:59 +01:00
wpetit 2a479a1f86 feat: add hydra-oidc component 2023-02-01 14:02:39 +01:00
wpetit 9e73054781 fix: use variable to determine postgresql service name 2023-01-30 16:38:56 +01:00
wpetit 06b7aa7903 feat: initial commit 2023-01-27 10:16:19 +01:00