[an error occurred while processing the directive]
![]() |
cosign-discuss at umich.edu |
general discussion of cosign development and deployment | |
java.security.cert.CertificateException: Untrusted Server Certificate Chain at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.a(DashoA6275)
Thanks, Cory
OK, I have the behavior reproducing now.
To see it, or generate more log entries, go to
http://csnavely.dev.deepblue.lib.umich.edu/
and click on any of the authentication-only options in the bottom left, like "My Deep Blue".
You will go to cosign-test.www.umich.edu and get the error message
"Unable to determine referring service from query string."
If I change the service name to something starting with "cosign-" instead, authentication will proceed but I get either a "too many redirects" from my browser or the looping page from CoSign.
Thanks!
Cory
Wesley Craig wrote:
We don't see anything in the logs on the weblogin.umich.edu. Perhaps we should have you point to cosign-test.www.umich.edu? We'll be able to see how your server is interacting with the cosign server better that way.
:wes
On 16 Mar 2005, at 08:59, Cory Snavely wrote:
A lame attempt to solve this by setting
Auth.Cosign.ServiceName=cosign-deepblue.lib
gets me further, but eventually fails with too many redirects. It is as if, after authenticating, that JCoSign doesn't recognize authentication has happened, and re-prompts (re-redirects).
Does this make any sense to anyone? I'm sort of at a loss here, but have the feeling this is something simple.