you should refer / re-use the methods of the SOAP-Gateway. By using them you will have no API-Change from OpenMeetings version to version. If you can separate the functions in an additional JAR File you should be save. You could try to use the Reflection example from the Crypt-Mode Manager to have a simple but flexible way of switching between different Auth and Database Versions.
sebastian 2008/11/4 smoeker <[EMAIL PROTECTED]> > > hi there, > > i am actually evaluating the possibility to implement a LDAP - > Authentification into OpenMeetings. > Before starting i thought, it would be a good idea to make it a public > issue - maybe there already is experience out there... > > i already implemented Ldap - Authentification into Java - apps, so the > main point for me would be , how to integrate it into OpenMeetings > without clashing with the built-in solution or another "in progress" > solution... > > Problems could be the selfregistering mode, so i would like to > implement the new AuthMethod additionally > (Ldap call only takes place, if user cant be found in the database, > Selfregistering only in the built-in database) and configurable (maybe > as part of the Install servlet routiene...). > > Would be glad about any kind of "best practice" in regard of > OpenMeetings, so as active help ;-) > > see ya > > Smoeker > > > -- Sebastian Wagner http://www.webbase-design.de http://openmeetings.googlecode.com http://www.laszlo-forum.de [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenMeetings User" 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/openmeetings-user?hl=en -~----------~----~----~----~------~----~------~--~---
