IdP v3: reload-service.sh

[Kirk Turner-Rustin]

On Tue, 29 Sep 2015, Cantor, Scott wrote:

>> Container's access log registered an HTTP redirect (302) for my curl
>> attempt, i.e.:
>
> Then that's the problem. The IdP doesn't return that.

Just to put closure on this:

We have tomcat configured to force (redirect) connections to port 8443. 
The reload-service.sh doesn't follow redirects (nor IMO should it need 
to), and the curl command line I unsuccessfully used didn't follow 
redirects either. So naturally I never got past the container's HTTP 
connector.

These commands worked just fine:

     Follow the redirect, ignoring SSL cert exchange requirements:

     # curl -kL \
 	http://localhost/idp/profile/admin/reload-service?id=[serviceId]

     Don't futz with redirects but go directly to the service URL,
     respecting SSL cert requirements.

     # JAVA_HOME=/usr ./reload-service.sh -id [serviceId] \
 	-ts /etc/pki/java/tomcat.keystore \
 	-tp [keystore-password] \
 	-u https://idp.owu.edu:8443

Thanks again to all.

Cheers,
Kirk

-- 
   Kirk Turner-Rustin SCJP  | Senior Systems Analyst
   Ohio Wesleyan University | Information Services
   http://www.owu.edu       | http://infoserv.owu.edu