Yes, good catch. The httpclient that proxy callbacks use is different from the httpclient that SLO uses, where the latter does not use the CAS local truststore.
Feel free to submit an issue, or better yet, submit a patch. From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of AxelR Sent: Sunday, December 13, 2015 8:27 AM To: CAS Community <cas-user@apereo.org> Subject: [cas-user] Re: CAS Single Logout request results in certificate_unknown (despite proxyreceptor is working fine) One additional information which increase my assumption that HttpRequestFutureTask.execute is not using the http.client.truststore.file definition: After importing the certificate to the default JRE cacerts file the PUT request works fine! Best regards, Axel -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
