Done. http://www.ja-sig.org/issues/browse/CASC-80
In the meantime i will try to customize my shibboleth to execute this
kind of piece of code at init-step (I don't know yet if it's easily
doable):
HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier() {
public boolean verify(String urlHostName, SSLSession session) {
return true;
}
});
Thank you,
Stéphane Gully
On Mon, Apr 6, 2009 at 3:25 PM, Marvin Addison <[email protected]> wrote:
>> In fact, i'm not sure this global parameter really exists... I'm not a
>> regular Java developer, i just imagined that this parameter could
>> exists :-) The real question i should ask is: is it possible to setup
>> a HostnameVerifier using CATALINA_OPTS ?
>
> Apologies, I missed the point of your question. There is no system
> property that I know of to globally set the hostname verifier for all
> HTTPS connections in the JVM. It would be a straightforward Java
> source modification to do this for CAS service ticket validation, but
> I realize that may not be an option for you. I do believe that
> exposing pluggable hostname verifiers via CAS configuration would be
> generally beneficial. I hope you'll consider creating a Jira
> improvement issue for that,
> http://www.ja-sig.org/issues/secure/CreateIssue!default.jspa.
>
> Regards,
> M
>
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
