HI,
 

I have made the validation url working now. 

The validation handler returns 0 after decode the query string.

However, it still won't let me get to the protected page. 

 

The filter redirects to the protected page after validation handler is done.

But it seems that the filter cannot find the cookies somehow, then it redirects 
to weblogin server again, going in a loop.

At this point I cannot find more about the problem. 

 

Another thing, i cannot find cosignd log on a mac. There is no syslog.log on 
mac os.

Just wondering where the cosignd could write to.

 

 

> CC: 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 
> 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:
> <ValidReference>^https?:\/\/www\.example\.edu(\/.*)?</ValidReference>
> 
> This will match pretty anything beginning within www.example.edu. If 
> the regex fails or if the cookie provided on the validation url is 
> invalid, the user is redirected to the URL specified in 
> <ValidationErrorRedirect>.
> 
> 
> Jarod
> 
> On Nov 9, 2009, at 3:47 PM, 文卓 张 wrote:
> 
> > 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 <validreference>.
> >
> > 1) what exactly do i have to put in the <validreference> tag.
> > my iis server is called 'lynx', the web application is 'BlueGateway',
> > the page i want filter to protect is '/BlueGateway/Cosign.aspx.
> > So, should i my validation URL be <validreference>http://lynx/ 
> > BlueGateway/Cosign.aspx</validreference> ?
> >
> > 2)Has the validation URL to be https? or I can just use http?
> >
> > Rightnow, from the logs, it seems that the weblogin authenticates 
> > successfully, and send back login cookies
> > in URL like 
> > http://lynx/BlueGateway/cosign/valid?cosign-IISDefaultService=loginCookies&returnpath
> >  
> > . But somehow
> > the browser directly go to the above location. From what i 
> > understand that the filter should intercepts this validation URL
> > and decode it then send user to the protected page.
> > So what am i doing wrong here.
> >
> > wenzhuo
> >
> > Get a great deal on Windows 7 and see how it works the way you want. 
> > See the Windows 7 offers now. 
> > ------------------------------------------------------------------------------
> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 
> > 30-Day
> > trial. Simplify your report design, integration and deployment - and 
> > focus on
> > what you do best, core application coding. Discover what's new with
> > Crystal Reports now. 
> > http://p.sf.net/sfu/bobj-july_______________________________________________
> > Cosign-discuss mailing list
> > Cosign-discuss@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/cosign-discuss
> 

                                          
_________________________________________________________________
Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail 
you.
http://go.microsoft.com/?linkid=9691817
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Cosign-discuss mailing list
Cosign-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to