Pete,
> We had it installed by a 3rd party so it’s a bit scary, which folders do I
need to backup?
Yes it *is* scary the first time you do it. However it is actually quite
easy and we have worked quite hard to make it impossible to shoot yourself
in the foot. Since you have to do about 30-50% of the work anyway I would
strongly suggest that you consider doing an upgrade either at the same time
or immediately before/afterwards since it will save hitting that learning
cliff twice.
I would also strongly suggest that you ping the nice guys at UK federation
support who will help you and point you at the latest documentation.
Andy, Karen
>> In my Shibboleth-tomcat configuration I just changed [...]
> I think it depends on how you deployed the application [...]
What Karen suggest will works and is a great way to debug the new file (I
used it when I out the default page together for the IdP). But as Andy says
unless you specify the "explode war" option in the deployment fragment (or
use the "copy the way file into webapps and let tomcat do it) you cannot
play it like that
FWIW (and remember I am a developer, not an IT guy) my recommendation is for
a *deployment* to use the deployment fragment with no explode. Then you
only have one version of the file and you cannot accidently change the live
version and not the real one (which means that after a restart your login
page can regress). I guess in a perfect world I would explode the war on my
development IdP and leave it compacted on the production one.
I'll also warn people that Tomcat caching can be idiosyncratic - you may
need to blast away the caches if you are not seeing the file you want.
And, although it’s a small benefit right now, this will be fixed in V3 of
the IdP. The login page won't be a jsp and so it won't have to be a war
file so in order to change the login page you won't have to mess with that
stuff.
FWIW YMMV & c
rod
|