- From: Oliver Trieu <>
- Subject: Re: [grouper-users] Keeping secrets secret
- Date: Mon, 27 Apr 2020 18:54:17 +0200
sorry to highjack your thread but had the same problem recently.
I used this method to externalize the passwords for my grouper
instance running on openshift (and thats basically kubernets with
This way you can mount the password files using secrets.
And you can put all your config files into version control since
they will not contain any passwords.
Am 27.04.2020 um 17:33 schrieb Alex
ElConfig has been supported for quite some time
(we've used it since 2.3 I know, but I think it goes back
On Mon, Apr 27, 2020 at 11:02
AM Poddar, Amit <> wrote:
is possible since which version of grouper?
on behalf of Alex Poulos <>
Monday, April 27, 2020 10:51 AM
Darren Boss <>
Mailing List <>
Re: [grouper-users] Keeping secrets
You can use env variables and read from these
within a config file. Here's an example:
(Note the .elConfig at the end of the config
parameter: this lets you use JEXL).
You can then populate DATABASE_PASSWORD however you
wish (k8s secret e.g.)
On Mon, Apr 27, 2020 at 10:42 AM Darren
Is there any documentation or guidance on
pulling out secrets from Grouper configuration
which is what I'm doing now by placing properties
files that contain secrets into Kubernetes secrets
but ideally I'd like to have these files under
version control and only store the passwords in a
system like K8s secrets or something like
Archive powered by MHonArc 2.6.19.