Skip to Content.
Sympa Menu

grouper-users - [grouper-users] RE : [Grouper API] Multiple grouper.client.properties files

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] RE : [Grouper API] Multiple grouper.client.properties files


Chronological Thread 
  • From: Nicolas Forney <>
  • To: Chris Hyzer <>, "" <>
  • Subject: [grouper-users] RE : [Grouper API] Multiple grouper.client.properties files
  • Date: Fri, 14 Jun 2013 07:49:09 +0000
  • Accept-language: fr-CH, en-US
  • Authentication-results: sfpop-ironport04.merit.edu; dkim=neutral (message not signed) header.i=none

Thank your for your help. 
I have finally used the GrouperClientUtils.grouperClientOverrideMap() method to resolve this problem.


De : Chris Hyzer []
Date d'envoi : mardi 11 juin 2013 17:57
À : Nicolas Forney;
Objet : RE: [Grouper API] Multiple grouper.client.properties files

My suggestion is if you don’t use prod from the test env, then don’t have that password and connect string there… so I think your build script should put the right properties file in the right env.

 

However, if you still want to go down that route, you can have blanks or defaults in the grouper.client.properties, then read your own properties from another file, and use this call to decorate the properties:

 

GrouperClientUtils.grouperClientOverrideMap().put("grouperClient.ldap.url", "ldaps://whatever");

 

https://lists.internet2.edu/sympa/arc/grouper-dev/2009-12/msg00005.html

 

Thanks,

Chris

 

From: [mailto:] On Behalf Of Nicolas Forney
Sent: Tuesday, June 11, 2013 9:00 AM
To:
Subject: [grouper-users] [Grouper API] Multiple grouper.client.properties files

 

Hello,

 

We import grouperClient.jar library in a Java application in order to use the Grouper API.

 

I’d like to know if there is a built-in solution to specify the name or path to the grouper.client.properties file at runtime.

 

I have to deploy our application in two different environments (production and test), so I’d like to be able to embed the application with two grouper.client.properties which contains different configurations (for example : grouper.client.prod.properties and a grouper.client.test.properties files). When the application is run on the prod or test server it should be able to load the corresponding grouper.client.[prod/test].properties file.

 

If it’s not possible, I can dynamically rename my prod or test grouper.client.porperties files when I deploy the application on the servers. However, I’d prefer a solution where I can handle this without having to copy or rename files.

 

Thank you for your help

 

 

Nicolas

 

 

Nicolas Forney

Université de Genève
DSTIC - NTICE

24 rue du Général-Dufour
1211 Genève
Bureau 360d
Tél. +41 22 379 12 97
http://www.unige.ch/stic

 

http://www.unige.ch/presse/charte/logos_unige/Administration_Rectorat/DSTIC/DSTIC.gif

 




Archive powered by MHonArc 2.6.16.

Top of Page