We've recently started using Jforum internally and we've done some work to integrate our separate user authentication systems into JForum using some of the informatin provided in the boards here for external login verification.
One of the next steps were thinking of taking is to use something like OSUser to abstract away the notion of the login into a separately manageable entity. We were wondering if anyone in the user community has done something like this, and if so, what the benefits and pitfalls were.
Otherwise, if we are to embark down this road ourselves, how useful would this be to JForum to be able to do this?
The other question I have is just a small issue. JForum seems reliant on log4j and I was wondering if it was possible to move to jakarta commons-logging instead of using log4j directly. Commons-logging provides a facade into a number of popular logging systems, so it can work with a larger number of providers. Additionally, commons-logging defaults to using log4j as the default provider, so it should be seamless for all users.
This is something we would definitely be interested in doing, as it would let us use the default codebase instead of constantly getting latest and applying a series of horrific patches.
Please let us know your thoughts
-a [originally posted on jforum.net by cilquirm]
We actually implemented a solution similar to the external authentication, and the biggest problem is that it requires some tricky code ( or constant synchronization ) to work.
The biggest issue for us is that it 'fakes' the initial login by "pushing" the user into the jforum database.
I was thinking of using OSUser more for the complete management of the user, instead of just login. i.e. out of the box, it can work just as exactly as jforum works now, by storing the user/group information directly into the databases, but can be extended/modified by third parties to get user/group information from external data sources.
But this may be worth a longer term discussion into the future.
As for commons-logging, would you like us to do this from the 2.02 release or from CVS. We'll get started on it ASAP.