on the one hand, you don't have to use the insecure passwords for authentication, but you can still use it for demographics.
(Yeah, read it again.) So what to do to create the users? create a spreadsheet from the insecure data and use it to create a batch of addCustomerUser.pl... bin/otrs.AddCustomerUser.pl -f *FirstName *-l *LastName *-p *password *-e *emailaddress *-c *CustomerID *(email address or something else) *username* then copy the result to the command line. not *perfect* in the sense of password *sync* but will get the job done. On Thu, Jun 6, 2013 at 1:27 PM, Adam Moffett <adamli...@plexicomm.net>wrote: > I have an existing billing system where the user's passwords happen to be > stored in MSSQL in plain text. This is an existing system written by > another company and I am not at liberty to change it. Is there any way to > configure OTRS to use an external backend with plain text passwords? > > I saw an old thread on the topic in the archives and the answer a few > years ago was "No"...any chance that's changed? > ------------------------------**------------------------------**--------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: > http://lists.otrs.org/**pipermail/otrs<http://lists.otrs.org/pipermail/otrs> > To unsubscribe: > http://lists.otrs.org/cgi-bin/**listinfo/otrs<http://lists.otrs.org/cgi-bin/listinfo/otrs> >
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
