Skip to Content.
Sympa Menu

grouper-study - Re: [grouper-users] Containerized Grouper and Secrets

Subject: grouper-study

List archive

Re: [grouper-users] Containerized Grouper and Secrets


Chronological Thread 
  • From: John Schrader <>
  • To: Jack Stewart <>
  • Cc: "Hyzer, Chris" <>, Christopher Hubing <>, "" <>, csp study grouper <>
  • Subject: Re: [grouper-users] Containerized Grouper and Secrets
  • Date: Sun, 29 Apr 2018 12:09:39 -0400
  • Arc-authentication-results: i=1; mx.umich.edu; iprev=pass policy.iprev=209.85.214.48 (mail-it0-f48.google.com); spf=pass ; dkim=pass ; dmarc=pass ; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; d=umich.edu; s=arc-2017-08-04; t=1525018181; c=relaxed/relaxed; bh=K2MujSNDvAAv4j3U3z2sk1Zsj7C1eK9W97I39AX33Dc=; h=In-Reply-To:References:From:Date:Subject:To:Cc; b=L5ltxoR/nMwiwHg13I45ToM9XIaYXsuJ9KCqwZL+DaCy7rSZtDTLGMLO/MQjJ/Pb3F90jb4CFqwwUTsmzP9lAZXGr3/pH+F8ODBfw4GL0OaSD7RtUOlhxWcCvoWI3AUaKHkGvT4hX5xA5UYPAQGLD46FuZa0Q0obDns943kybMsp8YpGHMRwyGxfDQxaeMoIv2GcfPG+k5XPlG332pOs+QOCz/88kfvh5NjMP61DffImr8RzyL5wpGlP8/jIutLmiNdYSsB4L8NdcgeTPWbG/n1amu6jLxZD04sUlxP/mkqxWe1L5mIvH70QCUV64jK/LJaQjZoOxTRhbMjkphxUxg==
  • Arc-seal: i=1; a=rsa-sha256; d=umich.edu; s=arc-2017-08-04; t=1525018181; cv=none; b=bnt2VNA+8eBlffZddiBhPZ0QKFeZ5A6ZHQfiZefB/F/nsptxlx7Qj4QLOM0/bv92slraCLiQim9CktjeTOoIMgTn9+d5LmhIio8GyUqSbdxi59UBQI8koCjMtjJXFT1w5E5G6m4htJMXyHFI8Q11HgSUXGj0kTlg6eplu682YV4wvXELQJgzSVS1zx+OyYl9BB6UWd8OdMqhFroOfIJwsvD3hZ1eE/XJvB09HJ/D6ZKXuVUAaSTHyOcLb4cqI5GO7zpFMxvX/pP95sWHNSiItpWvxOBtUDsH3eN352tf3WndgzyazyrsXgZHXyF1ehkIISTjVplRJYFXnLAMwSaa6g==
  • Ironport-phdr: 9a23:2TWkrRQ1VdehGyICewasYt3iFdpsv+yvbD5Q0YIujvd0So/mwa67ZBaAt8tkgFKBZ4jH8fUM07OQ7/i7HzRYqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjWwba98IRmssQndqtQdjJd/JKo21hbHuGZDdf5MxWNvK1KTnhL86dm18ZV+7SleuO8v+tBZX6nicKs2UbJXDDI9M2Ao/8LrrgXMTRGO5nQHTGoblAdDDhXf4xH7WpfxtTb6tvZ41SKHM8D6Uaw4VDK/5KpwVhTmlDkIOCI48GHPi8x/kqRboA66pxdix4LYeZyZOOZicq/Ye94RWGhPUdtLVyFZAIy8YYsBAeQCM+hFsYfyu0ADogGiCQS2Hu7j1iNEi33w0KYn0+ohCwbG3Ak4EtwKt3TUrNP1P7oPX++pzKnI1y/MYO5I1jfn9YPFdRQvofaMXbJ2a8bf1FUgFwPfjlqKtIPqISmV2/8Ls2eG9eZvS/+gi3M+pgx3vzOhyMAsiozTiYIUzFDJ7Th5wJwxJdGiU057ZMaoH4FVty6ANop2RcUiT3t0tyY9z70KoYa7czIRyJQ8yR/fbOaHfJWS7hL4UeadOTZ4hHR5eL2hnRay91avyvHiWsWuzllFszdFnsHXtn8TyxPT8NaISudm/kekwzmP0Rrc6u5aLkAuj6bbMYAuzaQtmZYLrETDBTH5mF/wjKCMc0Ur5PKk6//iYrjgu5SSNJd0hxn+P6gwgMCyD+Y1PhITU2SG++mwzqDv8VD6TblSkPE6jq3UvIrZKMkbvKK1HRJZ34k55xuwDDqr1skTk2MdI1JfYh2HipDkO1HQL/D8Cveym1WskDFwx/DBOr3uHJPNLmTanLf6ebZ99lRTyAUzzdxF+Z1UBasBL+zoWk/qrtDXFAU1MwmuzObmDNVxzJ4eWWeOAqCFMKPeq0GH6f8yI+WUZY8VvijyK+Q96vPuk3M1g1EQcKuz0ZcKdXy1HO5qL1iEbXfvmtsBFH0Fvgs6TOzkkl2CVjtTam6uUKIn/jE3EpmmDZveRo+wgL2Nxii7HodRZmBbElCDD23oe5yaVPcWciKSJdVhkicfWLi8To8h1A2htA/gx7V5M+XU5zUUtYj/29ht++3TiRYy+CR7D8SH1GGNUnl0kX0SRzMvx6B/vVF9xUqD0KVjh/xYFMdT5+9SUgskL5Lczup6C8zsVQLbeNeGVkqmTsu8DT4vU90x3oxGX0EoOdypjVj4wye1CqUJ3+iOBoco/730wn3wLMY7xnrbgvoPlV4jF+lINWvuvaV/7QHfCpSBx2eel6DsTq8cxifB+X2ry2bIsU1FBl0jGZ7ZVGwSMxOF5e/y4VnPGvr3Uewq

This is a great conversation..

For those of us running in AWS cloud, AWS has released "SecretsManager" [1]

SecretsManager opens up some interesting possibilities for both EC2 instances and containers(tasks) running in ECS.

As a POC, I've created an elConfig class (thanks to Chris for the capability) that retrieves values for hibernate properties:
hibernate.connection.url.sm.elConfig            = ${edu.internet2.middleware.grouperClient.config.SecretsManagerElClass.getSecret('/grouper/dev','url')}
hibernate.connection.url                        = "$$hibernate.connection.url.sm$$

hibernate.connection.username.sm.elConfig       = ${edu.internet2.middleware.grouperClient.config.SecretsManagerElClass.getSecret('/grouper/dev','username')}
hibernate.connection.username                   = $$hibernate.connection.username.sm$$

hibernate.connection.password.sm.elConfig       = ${edu.internet2.middleware.grouperClient.config.SecretsManagerElClass.getSecret('/grouper/dev','password')}
hibernate.connection.password                   = $$hibernate.connection.password.sm$$
from SecretsManager.

Read/Decrypt access to the `/grouper/dev` secret is controlled by the role associated with an EC2 instance or ECS task.
Using a role helps with the initial credential bootstrapping and allows for immutability.

-John









On Thu, Apr 26, 2018 at 1:27 PM, Jack Stewart <> wrote:
Everyone,

Thank you all for your wonderful feedback!  I hope the discussion continues.

A few thoughts:

- Although Grouper can run with environment variables, it would take a lot of time to convert, and each major upgrade could possibly be made tricky as a result.  Or am I being too paranoid?

- I don’t quite see consensus on a clear way forward.  All the information presented here has been helpful, though.  I will check what others are doing locally.

Jack


-- 
Jack Stewart
Solutions Architect, Identity and Access Management
University of Michigan

On Apr 26, 2018, at 12:39 PM, Hyzer, Chris <> wrote:

Fyi grouper config can happen in env vars, also the sources.xml can be migrated to subject.properties

https://spaces.internet2.edu/display/Grouper/Grouper+configuration+overlay#Grouperconfigurationoverlay-Environmentvariables

https://spaces.internet2.edu/display/Grouper/Grouper+sources.xml+conversion+to+subject.properties

Thanks
Chris

-----Original Message-----
From: [] On Behalf Of Christopher Hubing
Sent: Wednesday, April 25, 2018 1:00 PM
To: Jack Stewart <>
Cc: ; csp study grouper <>
Subject: Re: [grouper-users] Containerized Grouper and Secrets


For I2, we are storing secret things in an encrypted S3 bucket. The build
host has access to read from it, and then pushes the images to a private
Elastic Container Repo. The containers run in ECS.

Here's an example of our Dockerfile for the UI:
https://github.internet2.edu/gist/chubing/c4e663ab5a39fb73dccdcd748a92c5fe

Since the new Grouper container is pushed to Dockerhub (and have tags for
patches), it should make it pretty easy to manange (hopefully).

-c

On Wed, 25 Apr 2018, Jack Stewart wrote:

Everyone,
I would like to start out by saying that the new role-based Grouper containers are great!  It was very easy to build the images.

Now my question is, what are other schools doing with regard to their Grouper configurations?  Are you "burning them into" storing them in the containers themselves, or are you using
secrets?

Converting an application like Grouper to use secrets would be a LOT of work.  Effectively, you would need to convert all of the settings to environment variables.  How would you deal with
the sources.xml files which, by design, need to be customized?

Many thanks,
Jack


--
Jack Stewart
Solutions Architect, Identity and Access Management
University of Michigan
4251 Plymouth Road
Ann Arbor, Michigan 48105-3640
(734) 764-0853





--
John Schrader
Identity and Access Management
Office of Information Technologies
University of Notre Dame

EVERYTHING SHOULD BE MADE AS SIMPLE AS POSSIBLE, BUT NOT ANY SIMPLER
—ALBERT EINSTEIN



Archive powered by MHonArc 2.6.19.

Top of Page