|
|
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: Bug report
Hey Brett,
Thanks for heads up! :) We've made some changes to the way the cgi
handles errors, and have checked them into CVS. This bug fix will make
the 1.6 release. :)
-Johanna
On Apr 28, 2004, at 11:43 PM, Brett Lomas wrote:
Hi all,
The Cosign from the CVS (not sure if it is in the release) has a bug.
If the cosign CGI cannot find any cosignd connections (the
connlist_setup returns NULL) it continues processing. If the user
enters a valid username/password the cosign_login fails (no
connections) and they are redirected to the services page. I believe
this is incorrect behaviour, because are not logged in, as access a
protected site forces a login again (enter the credentials) because
the cosign ticket hasn’t been stored.
This could be very confusing to the user; I believe the error page
should be displayed if no cosignd connections could be found.
Thoughts
Brett
------------
Brett Lomas
Integration Architect
Information Technology Systems and Services
The University of Auckland
New Zealand
Phone: +64 9 3737 599 extn 86499
Mobile: +64 21 757 096
!DSPAM:40907a8321396210104589!
|
|