|
|
 |
cosign-discuss at umich.edu
|
|
general discussion of cosign development and deployment
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new jcosign service produces error message at authn
The CGI and daemon are looking for:
cosign-XXXXXX=
as the cookie. I believe the Apache and IIS filters force cosign- to
appear in the cookie. JCoSign must not.
:wes
On 14 Mar 2005, at 15:31, Cory Snavely wrote:
It is
https://weblogin.umich.edu/?
deepblue.lib=qa3enaniTO2elCoLA0VnlGuyDQaiNFW44etne4zkV8bsj2ghPgt3TMk7h+
N3dcU-qc8p+XBnh6hR0QPqhmPTaJn8dScZRxWmlAvqnVvXS9UkiERLe
+cwe4GPyDDjx3QgyAzp5RdO1j-JQDQW+lWrk9uusNikhVpk;&http://
deepblue.lib.umich.edu/dspace/password-login
Wesley D Craig wrote:
I know that error, for sure. It means that JCoSign didn't form the
"register" redirect properly. What's the full URL that you are
redirected to?
:wes
On 11 Mar 2005, at 16:20, Cory Snavely wrote:
I have JCoSign installed and mostly configured properly, I think,
with a brand new service.
I am seeing an error upon redirection to the authentication page:
Unable to determine referring service from query string.
What does this error indicate? Is this a certificate problem?
|
|
