Hi,
I'm trying to upgrade to Cosign filter 3.0 from version 2 right now.
However, i have encountered few problems and i have few questions about the
new tag .
1) what exactly do i have to put in the tag.
my iis server is called 'lynx', the web application is 'BlueGateway',
th
The validReference is a regular expression. The "returnpath" in your
example URL is compared against this to make sure the user is being
redirected to what is (probably) a legitimate URL. The example
provided in the sample.cosign.dll.config is:
^https?:\/\/www\.example\.edu(\/.*)?
This wi
: cosign-discuss@lists.sourceforge.net
> From: ja...@umich.edu
> Subject: Re: [Cosign-discuss] IIS 6 Cosign filter
> Date: Tue, 10 Nov 2009 11:16:09 -0500
> To: andrew...@hotmail.com
>
>
> The validReference is a regular expression. The "returnpath" in your
> ex
On Wed, Nov 11, 2009 2:42 PM, =?gb2312?B?zsTXvyDVxQ==?=
wrote:
> The filter redirects to the protected pageafter validation handleris done.
> Butitseems that the filter cannot find the cookies somehow, then
> itredirects to weblogin server again, goingin a loop.
> At this pointIcannot find more ab
Common causes of browser looping:
By default, the cosign service cookies are marked as secure, and will
not be transmitted over http connections. The recommend solution is
to redirect http requests for cosign-protected pages to the https
equivalent. You can also remove the "secure" flag i
On Nov 11, 2009, at 3:09 PM, Jarod Malestein wrote:
>
> Common causes of browser looping:
>
> By default, the cosign service cookies are marked as secure, and will
> not be transmitted over http connections. The recommend solution is
> to redirect http requests for cosign-protected pages t
uld
find more details about the problem.
Thank you for responding.
Wenzhuo Zhang
> From: admor...@umich.edu
> Date: Wed, 11 Nov 2009 15:42:34 -0500
> To: ja...@umich.edu
> CC: cosign-discuss@lists.sourceforge.net
> Subject: Re: [Cosign-discuss] IIS 6 Cosign filter
>
If you can find anything wrong, please let me know.
Wenzhuo zhang
From: andrew...@hotmail.com
To: admor...@umich.edu; ja...@umich.edu
Date: Wed, 11 Nov 2009 16:32:07 -0500
CC: cosign-discuss@lists.sourceforge.net
Subject: Re: [Cosign-discuss] IIS 6 Cosign filter
Hi all,
I have succe
On Nov 11, 2009, at 4:32 PM, 文卓 张 wrote:
> 3) The ports and certificates are fine, because I saw communications between
> filter and weblogin server in debug mode.
Unfortunately, cosignd -d doesn't tell you what the result of the CHECK is. The
only way to know for sure is to see what cosignd i
Hi all,
I have made the cosignd log work now. Thanks for the hints.
But it still doesn't give me much information either. Following is the
cosignd log during one time login:
--
No
The filter is validating the cookie with cosignd and issuing the Set-Cookie
header, but when you get redirected to the protected URL, your browser isn't
sending along the service cookie. (See my modified version of the debug log
below.)
Either your browser is set not to accept cookies, or the c
Wow, it works now, the problem is exactly what you said.
The hostname doesn't match. I used IP address in the cosign.conf for validation
URL.
Thank you.
Wenzhuo
> Subject: Re: [Cosign-discuss] IIS 6 Cosign filter
> From: admor...@umich.edu
> Date: Thu, 12 Nov 2009 16:06:44
12 matches
Mail list logo
