Emmanuel, thanks for the reply: > Simply move the authentication rule one step above: rather than using > "/project/login" for the authentication rule in your Apache config > file, use "/project"
I see what you mean, but I've just changed from Apache-based authentication to the Account Manager Plugin, using digest authentication (the main motivation was to allow the admin to add users online and for users to be able to change their passwords). How would your advice translate to that environment? > Anyway with the above trick, you won't have any anonymous anymore, so > this point won't apply anymore. Good, and I hope this will be true of the "translated" advice. >> - On logout, the user is left on the same page; I'd like to take them >> back to the welcome page. > > If you're using HTTP authentication, logout is not effective, the user > needs to close his browser or use a HTTP authentication clear feature > (availble in Firefox among others) I think, with this change, I'm not using HTTP authentication. In fact, I found that logout is definitely "more effective", in that I can now log out and log back in as a different user, which I couldn't do before. Still, when I log out, the URL stays at the last page I visited. I'm guessing there's a way for Trac to detect that a request isn't from an authenticated user, and redirect it to a standard welcome page, but I haven't found a way to make that happen. -- Don Dwiggins Advanced Publishing Technology --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
