My personal idea on that is that some kind of two level of authority is enough to keep CI password enough protected.<div><br></div><div>I mean. To reach CI you have to do a logon (1st) and then, agents, must be enabled via user-group administration (2nd).</div>

<div><br></div><div>Then I (and someone else) agree on some CI improvments as in <a href="http://bugs.otrs.org/show_bug.cgi?id=5711">http://bugs.otrs.org/show_bug.cgi?id=5711</a></div><div><br></div><div>What do you think ?</div>

<div><br></div><div>MV</div><div><a href="http://bugs.otrs.org/show_bug.cgi?id=5711"></a><br><br><div class="gmail_quote">On Fri, Oct 22, 2010 at 1:17 PM,  <span dir="ltr">&lt;<a href="mailto:asdrub@gmail.com">asdrub@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi itsm People!<br>
<br>
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?<br>
(this last one is my favorite choice)... Its possible to build an ci class with this features?<br>
<br>
Thanks in advance.<br>
<br>
Eduardo Ribeiro<br>
Rio de Janeiro - Brazil<br>
Enviado do meu BlackBerry® da Oi.<br>
---------------------------------------------------------------------<br>
OTRS mailing list: itsm - Webpage: <a href="http://otrs.org/" target="_blank">http://otrs.org/</a><br>
Archive: <a href="http://lists.otrs.org/pipermail/itsm" target="_blank">http://lists.otrs.org/pipermail/itsm</a><br>
To unsubscribe: <a href="http://lists.otrs.org/mailman/listinfo/itsm" target="_blank">http://lists.otrs.org/mailman/listinfo/itsm</a><br>
</blockquote></div><br></div>