[kforge-dev] trac, permissiong working (and working together)

[Rufus Pollock]

John Bywater wrote:
> Rufus Pollock wrote:
> 
>> After plenty of random bug pain we finally have trac working together 
>> with the permission system. You can check this out by going to:
>>
>>   http://test.kforge.net/annakarenina/trac/trac/
> 
> 
> 
> I don't get a trac service at this location. I get an error:
> 
> "ImproperlyConfigured: You need to specify both DATABASE_NAME and 
> DATABASE_USER in your Django settings file."

Dammit wrong url, should be:

http://project.test.kforge.net/annakarenina/trac/trac/

Remember all services themselves are available under the 'project' 
address scheme and all admin (django part) is available at 
admin.test.kforge.net (and at test.kforge.net currently). Sorry to cause 
confusion with this wrong url ....

>> and seeing that
>>   a) you will need to log in
>>   b) these credentials will work:
>>     username: levin
>>     password: levin
> 
> 
> 
> I could log in as levin here:
> 
> http://test.kforge.net/
> 
> :-)

You will also be able to access services themselves with the same user name.

>>
>> One rather cool thing is even though our authentication is entirely 
>> seperate from trac's system trac seems to automagically pick up our 
>> authentication (so if you log in as X this will be displayed by trac). 
>> Assume this is because we are using mod_python auth.
> 
> 
> 
> Great. Are we sure it isn't the whole realm that's authenticated, such 
> that somebody has access to everything once they have authenticated 
> somewhere. Just wondering....

Well yes, firefox or whatever browser tends to cache http authentication 
data and will resend it for new urls. This isn't done by the server 
however. To implement proper 'single sign-on' for services we wouldwould 
need to set up a cookie scheme. But that's another story ....

[snip]

Regards,

Rufus