ComAuthenticationLevel coding group
The possible values for the COM Authentication Level.
To access the code of the codings below, append the coding group name and coding name to
see an example below.
|CALL||4||Only the headers of the beginning of each call are signed. The rest of the data exchanged between the client and server is neither signed nor encrypted. Most SSPs do not support this authentication level and silently promote it to Packet|
|CONNECT||3||The normal authentication handshake occurs between the client and server, and a session key is established but that key is never used for communication between the client and server. All communication after the handshake is nonsecure|
|DEFAULT||2||COM chooses the authentication level by using its normal security blanket negotiation. It will never choose an authentication level of None|
|NONE||1||No authentication is performed during the communication between client and server. All security settings are ignored. This authentication level can be set only if the authentication service level is None|
|PACKET||5||The header of each packet is signed but not encrypted. The packets themselves are not signed or encrypted|
|PACKET_INTEGRITY||6||Each packet of data is signed in its entirety but is not encrypted. Because all of the data is signed by the sender, the recipient can be certain that none of the data has been tampered with during transit|
|PACKET_PRIVACY||7||Each data packet is signed and encrypted. This helps protect the entire communication between the client and server|