Re: [netconf] UserId for authentication in https-notif

[Mahesh Jethanandani <[e-mail]>]

Hi Balasz,

> On Oct 11, 2019, at 2:43 AM, Balázs Lengyel <balazs.lengyel=[e-mail]> wrote:
> 
> Hello,
> What userId will be used to perform access control on outgoing notifications transferred via https?

This was also discussed in an earlier thread, when Martin brought up the broader question of whether we are planning on using PUT or POST, to which URI, and authorization. 

Kent suggested that user-id will be part of http-params supported by the http client/server draft, and will be the user-id used by NACM. The example in the draft will be augmented thus:

<receivers
     xmlns="urn:ietf:params:xml:ns:yang:ietf-https-notif">
     <receiver>
       <name>foo</name>
       <tcp-params>
         <remote-address>my-receiver.my-domain.com <http://my-receiver.my-domain.com/></remote-address>
         <remote-port>443</remote-port>
       </tcp-params>
       <tls-params>
         <server-authentication>
           <ca-certs>explicitly-trusted-server-ca-certs</ca-certs>
           <server-certs>explicitly-trusted-server-certs</server-certs>
         </server-authentication>
       </tls-params>
       <http-params>
         <client-identity>
           <basic>
             <user-id>my-name</user-id>
             <password>my-passsord</password>
           </basic>
        </client-identity>
        <path>/some/path</path>
       <http-params>
     </receiver>
 </receivers>

Cheers.

>  
> regards Balazs
>  
> -- 
> Balazs Lengyel                    Senior Specialist                       Ericsson Hungary Ltd. 
> Mobile: [phone]              email: [e-mail] <mailto:[e-mail]>
>  
> _______________________________________________
> netconf mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/netconf <https://www.ietf.org/mailman/listinfo/netconf>
Mahesh Jethanandani
[e-mail]