Well, first of all, if the user does not exist in db "project_b", then why should they have access to the "project_b" site?
Assuming you got that turned around and the user has proper access to both, you would have to set a session variable or something that gets checked at every project change or access. If you are basing the different projects per directory, you can check the server variables for path info then do your security checks or whatever.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to find the best way to expire a user on one database when they go directly to another URL like the Following:
1. User login at http://bugtracker/directory_a which uses db "project_a"
2. User does not exist in db "project_b"
3. User points browser to http://bugtracker/project_b which uses db "project_b" and is able to access site.
Any ideas?
Well, first of all, if the user does not exist in db "project_b", then why should they have access to the "project_b" site?
Assuming you got that turned around and the user has proper access to both, you would have to set a session variable or something that gets checked at every project change or access. If you are basing the different projects per directory, you can check the server variables for path info then do your security checks or whatever.