Wcf security session 2

8
Transfer Security Modes

Transcript of Wcf security session 2

Page 1: Wcf security session 2

Transfer Security Modes

Page 2: Wcf security session 2

Objectives

• Five modes offered for accomplishing three aspects of Transfer Security– None– Transport Security– Message Security– Mixed – Both

Page 3: Wcf security session 2

• Turned off• No Client Credentials provided to Service• Highly inadvisable

None Transfer Security Mode

Page 4: Wcf security session 2

entry point

Transport Transfer Security Mode

• Secure Communication Protocol• Encrypts the channel• Integrity ,No Encryption key – corrupt message• Privacy, No other party other than recipient• Mutual Authentication

• Assumption– Client and Service negotiate details of encryption– Hardware acceleration

• Downside– Point-to-point– Only by intranet applications

Page 5: Wcf security session 2

Boolean

character

integer

Message Transfer Security Mode

• Encrypts the message• Securely communicate over non-secure transports

Page 6: Wcf security session 2

variables

• Uses Transport for Message integrity and Privacy as well as Service authetication

• Message security for Client Credentials

• Downside– Point to point– Rarely use this

Mixed Transfer Security

Page 7: Wcf security session 2

literals

expression

error, x not set

Both Transfer Security mode

• Message is encrypted• Transport channel is encrypted• Maximizes Security

• Overkill performance

Page 8: Wcf security session 2

Summary

• None is highly inadvisable• Transport works good in Intranet apps• Message suits for Internet apps• Mixed rarely used by developers• Both kills performance