<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Olle!<br>
<br>
Let's consider that our customer, that want's at all costs to have this
authentication being performed by Asterisk (on a different
fashion than provided by current alternatives), allow us to engage an
effort to implement some authentication API.<br>
<br>
First question that comes to mind is how common could be the use of
such API? I mean, as long as I could see, SIP and IAX channels could
use such resource. Is this feature extendable to other channels?<br>
The really important question: should we develop a
structured authentication API (with register/unregister/access
methods), or just create an authentication resource and use it on
necessary channels without the "knowledge" of Asterisk as it was done
so
far?<br>
<br>
If you decide to implement an authentication API (and I strongly vote
for that), will it be easy to
define the interface in order to be able to perform authentication on
the way needed by each channel ? Or maybe to point out a set of
parameters that will be enough for all current and future
authentication needs (like userid, password, domain, etc) ?<br>
For example: SIP provides a challenge mechanism based on HTTP
authentication, and for it we need only userid, password and domain.
But, how authentication works for the others "channel
entitites" (IAX, etc) ?<br>
<br>
How about an initial set of methods like this:<br>
<br>
struct channel_auth_engine<br>
{<br>
void authenticate(const char* userid, const char* password, const
char* domain); ***<br>
};<br>
<br>
*** Maybe we can define a method signature for each type of channel
(like: "sip_authenticate", "iax_authenticate", etc) with their
different needs of parameters;<br>
<br>
ast_channel_auth_engine_register (file main/channel_auth.c): receives a
"channel_auth_engine" pointer and a "char *" with the name of the
channel (like SIP, IAX, etc) on which this engine should be used, and
registrate it;<br>
ast_channel_auth_engine_unregister (file main/channel_auth.c):
unregistrate a channel auth engine;<br>
ast_channel_auth_engine_get (file main/channel_auth.c): receives a
channel name (like SIP, IAX, etc) and returns it's registered auth
engine, if any;<br>
<br>
On this initial view, I was not considering the possibility of someone
wanting to handle authentication differently on one same Asterisk
instance, so it will exist only one channel auth engine per channel
type.<br>
And this suggestion is intended just to provide additional, and/or
proprietary authentication handling to "channel entities".<br>
<br>
Any comments, ideas, disagreements ?<br>
<br>
Thanks and best regards,<br>
Mauro.<br>
<br>
<br>
<br>
<br>
<br>
Olle E. Johansson escreveu:
<blockquote cite="mid:0B78EFDE-3E5A-43BE-B758-9339F5244B57@edvina.net"
type="cite">
<pre wrap="">7 aug 2009 kl. 22.58 skrev Mauro Sergio Ferreira Brasil:
</pre>
<blockquote type="cite">
<pre wrap="">Hello there!
I was having a look on alternative ways to handle SIP users
authentication other than local/static and through ARA when I found
ticket <a class="moz-txt-link-rfc2396E"
href="https://issues.asterisk.org/view.php?id=5424">"https://issues.asterisk.org/view.php?id=5424"</a>.
Unfortunately this ticket was put on hold since 2007.
I found other people with similar needs than mine, that is a way to
make Asterisk use external means (mostly some sort of server) to
authenticate SIP users, and it seems that it could be usefull to IAX
users as well.
The question is: Why has this ticket got abandoned? Not enough
people interested? Not enough people/time available to handle it?
</pre>
</blockquote>
<pre wrap=""><!---->
Yes, yes.
/O
_______________________________________________
--Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext"
href="http://www.api-digital.com">http://www.api-digital.com</a>--
AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: <a class="moz-txt-link-freetext"
href="http://www.astricon.net">http://www.astricon.net</a>
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext"
href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="Content-Language" content="pt-br">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; ">
<title>TQI - Technology and Quality on Information</title>
<table style="border-width: 0pt; border-collapse: collapse;"
id="AutoNumber1" border="1" bordercolor="#111111" cellpadding="0"
cellspacing="0" height="151" width="46%">
<tbody>
<tr>
<td style="border-style: none; border-width: medium;" height="17"
width="96%"> <sub><u>At.,
</u></sub></td>
</tr>
<tr>
<td style="border-style: none; border-width: medium;" height="32"
width="16%"> <img src="cid:part1.06050209.01040609@tqi.com.br"
border="0" height="23" width="150"> </td>
</tr>
<tr>
<td style="border-style: none; border-width: medium;" height="12"
width="100%"><b><font face="Verdana" size="1">Technology and Quality
on Information</font></b></td>
</tr>
<tr>
<td style="border-style: none; border-width: medium;" height="13"
width="100%"><font face="Verdana" size="1">Mauro Sérgio Ferreira Brasil</font></td>
</tr>
<tr>
<td style="border-style: none; border-width: medium;" height="14"
width="100%"> <font face="Verdana" size="1">Coordenador de Projetos e
Analista de Sistemas</font></td>
</tr>
<tr>
<td style="border-style: none; border-width: medium;" height="14"
width="100%"><font color="#0000ff" face="Wingdings" size="2">+</font><font
face="Courier New" size="2"> </font> <font style="font-size: 9pt;"
face="Courier New"> <a href="mailto:@tqi.com.br">mauro.brasil@tqi.com.br</a></font></td>
</tr>
<tr>
<td style="border-style: none; border-width: medium;" height="14"
width="100%"><font color="#0000ff" face="Wingdings" size="2">:</font><font
face="Courier New" size="2"> </font> <font style="font-size: 9pt;"
face="Courier New"> <a href="http://www.tqi.com.br">www.tqi.com.br</a></font></td>
</tr>
<tr>
<td style="border-style: none; border-width: medium;" height="14"
width="100%"><font color="#0000ff"><font face="Wingdings" size="2">(</font><font
face="Courier New" size="2"> + 55 </font> <font
style="font-size: 9pt;" face="Courier New">(34)3291-1700</font></font></td>
</tr>
<tr>
<td style="border-style: none; border-width: medium;" height="14"
width="100%"><font color="#0000ff"><font face="Wingdings" size="2">(</font><font
face="Courier New" size="2"> + 55 </font> <font
style="font-size: 9pt;" face="Courier New">(34)9971-2572</font></font></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>