My personal idea on that is that some kind of two level of authority is
enough to keep CI password enough protected.
I mean. To reach CI you have to do a logon (1st) and then, agents, must be
enabled via user-group administration (2nd).
Then I (and someone else) agree on some CI improvments as in
http://bugs.otrs.org/show_bug.cgi?id=5711
What do you think ?
MV
http://bugs.otrs.org/show_bug.cgi?id=5711
On Fri, Oct 22, 2010 at 1:17 PM,
Hi itsm People!
How do you usually handle login/ passwords information in yours CI documentation plans at Otrs::itsm? Using external sw or itsm mod could handle passwords with DB crypto + agents ACL features? (this last one is my favorite choice)... Its possible to build an ci class with this features?
Thanks in advance.
Eduardo Ribeiro Rio de Janeiro - Brazil Enviado do meu BlackBerry® da Oi. --------------------------------------------------------------------- OTRS mailing list: itsm - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/itsm To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm