OsUser bug fixed!

Ok, I have fixed the bug.  It was a matter of us calling a method that 
sent us into a bad recursion.  I'm updating the isLoggedIn and 
isNotLoggedIn taglibs to check the newest cookies and session attributes 
then you should be able to test out everything in the system.  All we 
need to get in now is some security so that the admin console can be 
locked down.

Thanks,
Matt

Matthew Schmidt wrote:

> Yet another update on the OSUser bug.  It appears that the stack 
> overflow is coming from a call to a JLCPUser.getInternalUser().  It 
> throws the stack overflow even on a simple call like 
> jlcpUser.getInternalUser().getClass() in DefaultAuthenticator.  This 
> appears to be very weird to me, because its not even getting to the 
> credential provider to attempt an authentication.
>
> -Matt
>
> Matthew Schmidt wrote:
>
>> Team,
>>    We are in the process of moving all our processes over to some new 
>> machines at rackshack.  Because of this, IPs will change for the 
>> mailing list, the website, jira and the archives.  Currently, Jira is 
>> the only thing of JLCP switched over and it could take a little while 
>> for the DNS to propogate.  I have yet to decide if its running better 
>> yet.  Please let me know if you are experiencing performance problems 
>> with it.  The new machine is faster, so we'll see.  If you can't 
>> reach the mailing list this afternoon it will be due to it moving as 
>> well.  Just hang in there until I get it all moved :)
>>
>> -Matt
>>
>