Hi Atif, On Mon, Jun 03, 2002 at 11:09:27PM +0200, Atif Ghaffar wrote:
The users/groups/queues design is fixed to DB. Because the database_user_id (also database_group_id and database_queue_id) is used as reference for owner, ... and in some big selects (one select is faster then 2 or more).
Yup, I've been a bit through the code. Its very much tied to the DB. Perhaps in future releases, we can put a bit of abstraction so its not tied to anything. (just an idea)
It's a good idea. A good way.
Solution: * It's easy to add LDAP support for the OpenTRS authentication (Kernel/System/Auth.pm).
I would prefer
Kernel/System/Auth/Driver1.pm Kernel/System/Auth/Driver2.pm Kernel/System/Auth/Driver3.pm
This way, most DB/LDAP/XML specific stuff can be in the Drivers, where as Kernel/System/Auth.pm, just worries about authentification.
That's is correct. Horde is a nice example for this.
* How about a sync-script (e. g. ldap2db.pl) to sync the OpenTRS user table with LDAP (e. g. via cron).
Yes, that is also another possibility. Do you have API docs?
Not yet. But in Kernel/System/ you find all system modules. E. g. to add new user (User.pm->UserAdd()) ... Sorry, but just the code.
It would be much work to split users/groups/queues from the database. Maybe a feature for a new major release?!
I'll see what I can do to help you.
Cool! ;-)
-- Atif Ghaffar
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson