Shibboleth Developers

[Chad La Joie <>]

Okay, I tried to limit the number of things people had to fiddle with in 
the configure file.  Now there are 4 things you have to touch, and one 
optional one.  Do the instructions look better to people?

Chad La Joie wrote:
> How would I put it in the idp.xml in such a way that the configuration 
> would be shared amongst handle and/or artifact mappers?  I don't think 
> there is currently a way to do that.
>
> So, I'm thinking, for now at least, I'll just try to generate a much 
> better, production quality, configuration file and then just document 
> like 3 or 4 options people should/could fiddle with.  So, for example, 
> I'd probably drop all mention of the UDP stuff and just tell people to 
> use TCP and put their IP addresses in the correct place.  Drop mention 
> of the synchronous/asynchronous and make it synchronous, etc.  Just 
> limit the options we tell people about.  It'll still be an ugly file, 
> but at least people can ignore 99% of it.
>
> Later on, if we integrate this in to the Shib src we can make the 
> configuration a lot cleaner and user friendly because the code will have 
> access to APIs that extensions don't currently.
>
> Walter Hoehn wrote:
>
> > Excellent!  My one comment is that some of these configuration  
> > options don't really make sense or are sub-optimal for a production  
> > IdP.  So, maybe you could have a MUCH simpler configuration syntax to  
> > put inline into idp.xml.  This syntax would assume a lot of the  
> > configuration options and the more complex configuration could be  
> > generated from it.
> >
> > -Walter
> >
> >
> > On Aug 24, 2005, at 7:13 PM, Chad La Joie wrote:
> >
> > > I believe I finished up the majority of the coding on the high  
> > > availability (load balancing/fail over) extension I was working,  
> > > however I need some advice on some thing.  The current  configuration 
> > > file for the intra-node replication mechanism is a  bear, and I'm 
> > > unsure how to make it easier.  One thought I had was  to put an 
> > > element for each bit configuration data in the idp.xml  NameMapping 
> > > element (which I'd then read and use in the code) but  I'm not sure I 
> > > like that, I think it might be to confusing or  cluttered.  Anyways, 
> > > please take a look at the Configuring HA Shib,  in the following 
> > > document, and give me some feedback on what you'd  like to see if you 
> > > were deploying this at your university.
> > >
> > > http://middleware.georgetown.edu/dokuwiki/doku.php/ 
> > > projects:hashib:usagedoc
> > >
> > > Also, if you look at the code and have some suggestions those are  
> > > welcome too.  I have not yet tested the code so I would suggest  
> > > going out and installing it, it probably wouldn't work.
> > >
> > > Thanks for the help.
> > > --
> > > Chad La Joie             315Q St. Mary's Hall
> > > Project Sentinel         202.687.0124

--
Chad La Joie             315Q St. Mary's Hall
Project Sentinel         202.687.0124