[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Perspectives for enabling Third Party Authentication with "NETCONF over TLS"

On Tue, Feb 26, 2008 at 05:34:30PM +0100, Mohamad Badra wrote:

> I think we front the issue of defining correctly a common mechanism to 
> enable using an authentication function for the manager via third parties.
>
> There are many ways to move forward with third party authentication. Below 
> three of them, sorry for this long mail. Any advice is wellcome...

[...]

I only see two options here:

a) Extending NETCONF with an authentication mechanism that can hook into
   SASL (which would be something for NETCONF to work on)

b) Getting TLS enhanced that it can do client authentication with passwords
   and such things natively (which is clearly not NETCONFs business)

I guess the answer will be given by the security folks. I believe we
need to seek security area advise here.

/js

PS: My understanding is that BEEP does hook into SASL so I don't think
    BEEP is an issue here.

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>