Benjamin Staffin 64c94bd40a nixos/keycloak: Add systemd startup notification ... This makes it possible for other systemd units to depend on keycloak.service using `after` and `wants` relationships, and systemd will actually wait for Keycloak to finish its initialization before starting any dependent units. This can be important for services like oauth2-proxy, which (when configured to use Keycloak as its auth provider) will fail to start until Keycloak's `.well-known/openid-configuration` endpoint is available.		2024-05-14 14:26:35 -04:00
..
keycloak-discord	keycloak.plugins.keycloak-discord: 0.3.1 -> 0.5.0, set sourceProvenance	2024-03-05 22:17:51 -05:00
keycloak-metrics-spi	keycloak.plugins.keycloak-metrics-spi: 4.0.0 -> 5.0.0	2024-03-05 22:13:07 -05:00
keycloak-restrict-client-auth	keycloak.plugins.keycloak-restrict-client-auth: 23.0.0 -> 24.0.0	2024-03-05 22:11:04 -05:00
scim-for-keycloak	keycloak.scim-for-keycloak: kc-15-b2 -> kc-20-b1	2023-08-29 13:58:32 +02:00
scim-keycloak-user-storage-spi	keycloak-scim-user-storage-api: 20230710 -> 20240214	2024-02-25 11:56:28 +02:00
all-plugins.nix	nixos/keycloak: Add systemd startup notification	2024-05-14 14:26:35 -04:00
config_vars.patch
default.nix	keycloak: 24.0.2 -> 24.0.3	2024-04-17 01:14:04 +00:00