From: Greg M. <gm...@gm...> - 2008-12-20 14:25:08
|
IMO, The answer to this resides in using external authentication methods to applications and not the custom-built internal ones. If your Joomla install made use of an external LDAP service for authentication, you'd be all set. I think building another model for one application to authenticate to another would amount to reinventing something that already exists. \\Greg joomlagate.com wrote: > Hello! > > Tikiwiki is called CMS. It seems that it can do everything. Sorry for my disagreement, I use Tikiwiki ONLY for its Wiki feature. > > In fact, I choose Tikiwiki for wiki feature because of its Massive Online Translation function driven by CLWE. > > My website, http://www.joomlagate.com , is a website built with Joomla CMS. Where has a user pool of over 13 thousands. > > After I installed Tikiwiki, I want to limit the Edit/Create permission to login in users. > > But, I can't find a way to transfer all my 13,000+ users to Tikiwiki easily. > > Though Tikiwiki offered a method of batch uploading users by CSV file, Joomla has no feature to export a CSV file with non-encrypted passwords. > > I have an idea to solve this problem: Can we let Tikiwiki's login form connect to Joomla's user table to validating the login info? > > Let's expand this situation, not only Joomla, maybe some users has other program running together with Tikiwiki. Can we add such an option to let the Admin choose which user database will Tiki use to make login authentication? > > Is it possible? > > Thanks. > > > With best regards, > joomlagate.com. > > http://www.joomlagate.com > ------------------------------------------------------------------------------ > _______________________________________________ > Tikiwiki-users mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-users > > |