Shibboleth Developers

[Nate Klingenstein <>]

The snippet cited below is a part of a broader issue where pieces of the Java SP's configuration differ from the naming and structure of the C++ SP; in this particular example, default metadata will differ.  I've also run into a handful of places where the main configuration is different through trying to use configuration files for one in the other.

How hard do we want to try to unify the configuration further?  Is it a stated goal to be able to interchange the Java and C++ SP with no change to metadata or major configuration differences in sp.xml/shibboleth.xml, with the web server specific stuff mostly contained in server.xml/web.xml/httpd.conf?

I only ask because based on my tinkering so far it seems like it might be possible, so this might be a silly question.  If not, I might try to restructure the documentation because I'd assumed once a certain point were reached everything further would be done in a similar fashion.

On Oct 20, 2005, at 1:10, Howard Gilbert wrote:

Well, the problem here is that there is no context. There should be a

/shibboleth-sp between the 8443 and the Shibboleth.sso. Probably left it out

of the handlerURL.