Skip to Content.
Sympa Menu

shibboleth-dev - Re: More defined custom extensions mechanism

Subject: Shibboleth Developers

List archive

Re: More defined custom extensions mechanism


Chronological Thread 
  • From: Tom Scavo <>
  • To: Walter Hoehn <>
  • Cc: Chad La Joie <>, Shibboleth Developers <>
  • Subject: Re: More defined custom extensions mechanism
  • Date: Wed, 6 Jul 2005 17:30:43 -0400
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=q7wcYm6ab58MRuCV5MkFzL3a0UV0A8fJsO/GdbMkW/CQOsUGUvuVHVhMxLjlpqrlVuWDSgW/jCyV7Aldc0uUrmphHUmFMxT5w8f0vJMFobJXLvx7F5n2MGjAFOOFCoV/mn9O9plU8snCGiZIzmiHKUtjE0rtZaEVBQe1TYz454Y=

On 7/6/05, Walter Hoehn
<>
wrote:
> On Jul 6, 2005, at 4:03 PM, Tom Scavo wrote:
>
> > Are you suggesting that the plugin directly read the definitive
> > versions of the metadata and gridmap files stored in the GridShib home
> > directory (or the IdP home directory if we go that route)? I'm not so
> > sure this is a good idea. Shouldn't the files in $IDP_HOME$ be copied
> > over to the tomcat directory after they've been modified?
>
> Depending on the tomcat configuration, this might not even be
> possible. Tomcat can run without expanding the .war files (that's
> how I do it). As Scott mentioned, the whole reason we moved to the
> model of a separate configuration directory, $IDP_HOME$, is because
> folks didn't understand the process of updating the contents of .war
> files.

Good point. So I'm back to my original question: Does the plugin
directly read the files in $IDP_HOME$? Is that the recommended
approach?

Thanks,
Tom



Archive powered by MHonArc 2.6.16.

Top of Page