Use the following table to determine which security options and protocols are available for each type of session in Extra! 9.6 and later.
|
Session |
Available Security Protocols |
|||||
|---|---|---|---|---|---|---|
|
Encryption |
FIPS 140-2 |
Certificates† |
Authentication Tokens‡ |
End-to-End Encryption‡ |
ID Mgmt ‡ |
|
3270 |
No |
Yes |
Yes |
Yes§ |
Yes |
|
|
Yes |
Yes |
Yes |
Yes |
||
|
5250 |
No |
Yes |
Yes |
NA |
Yes |
|
|
Yes |
Yes |
NA |
Yes |
|||
|
VT - Telnet |
No |
Yes |
Yes |
NA |
Yes |
|
|
Yes |
Yes |
NA |
Yes |
|||
|
VT - SSH |
Yes |
Yes |
No |
NA |
Yes |
|
|
6530 |
|
No |
Yes |
No |
NA |
Yes |
† Supported certificates include self-signed certificates and those issued by a Certificate Authority (CA). To use certificates successfully, you must know how they are handled for your server. For more information, see Authenticating with Certificates in Extra!.
‡ Requires installation of Management and Security Server and configuration of the Reflection Security Proxy.
§ End-to-end encryption allows IBM mainframe emulation sessions to combine Express Logon and the user authorization feature of Management and Security Server.
|| SHA256 values are only supported via client and server certificates.