Here's the problem. We have different "portals" all running under the same server; each "portal" can potentially have its own database instance/login. For example, the "ABC" portal uses the database instance "ABC_INST", the "DEF" portal uses the database instance "DEF_INST", etc. Currently, I have the TR.props file specifying something like:
database.default.driver=oracle.jdbc.driver.OracleDriver database.default.url=jdbc:oracle:thin:@dataserver:1521:ABC_INST database.default.username=user database.default.password=pass The problem, of course, is that using these properties, I can only tell the server to point to one database instance per web app, not one per "portal." So, I want to be able to somehow use two different database setups for user logins to these two different "portals." The fact that the properties above say "database.default..." give me hope that I might be able to tell authentication which database setup to use on a user-by-user basis. (In my code, I can tell from the URL which portal the user is on, and I'm already overriding the default User object and Login action, but my Login action right now just calls the default Turbine action to actually log the user in. The solution I'm hoping to hear would have me passing some kind of parameter from my custom Login action to specify which database to use. But I don't see any such parameter in TurbineSecurity.) Thanks for any help, <>< gary -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
