wcf binding - WCF netTCPBinding -
wcf's nettcpbinding "secured default". understand means that..
- callers authenticated using windows credentials.
- messages signed
- messages encrypted.
however, can set basic wcf client service set on localhost. authentication work on same machine, how signing , encryption work?
wcf needs certificate sign , encrypt messages. if dont have certificate how service manage work? how message - going same machine signed , encrypted.
thanks.
by default nettcpbinding uses transport security, default characteristics list.
signing , encryption of messages in context not mean same thing in message security. rather means packets of data sent on network transport signed , encrypted. not rely on certificates. done security providers installed in operating system on sending , receiving machines, invoked via sspi (security support provider interface) - same mechanism involved, example, when domain credential used access resource such file on different machine on network.
before application data sent on connection, binding orchestrates sspi handshake between sender , receiver, specifying negotiate
security package (this chooses either ntlm or kerberos actual security protocol, depending on capabilities of respective host machines). security tokens exchanged on connection part of handshake, @ end of 2 sides' security providers have agreed session keys use in signing , encryption of ensuing application messages.
Comments
Post a Comment