srvcon_auth - Authentication type for incoming connections at the server configuration parameter
This parameter specifies how and where user authentication is to take place when handling incoming connections at the server; it is used to override the current authentication type.
Important: The SERVER_ENCRYPT
authentication type is deprecated, and the SERVER_ENCRYPT_AES
authentication type will not work in strict FIPS mode when FIPS 140-3 certified cryptographic
modules are introduced in a future version of Db2. For more information on the deprecation, see
Authentication methods for your server.
- Configuration type
- Database manager
- Applies to
-
- Database server with local and remote clients
- Database server with local clients
- Partitioned database server with local and remote clients
- Parameter type
- Configurable
- Default [range]
- NOT_SPECIFIED [NOT_SPECIFIED; CLIENT; SERVER; SERVER_ENCRYPT; KERBEROS; KRB_SERVER_ENCRYPT; GSSPLUGIN; GSS_SERVER_ENCRYPT; SERVER_ENCRYPT_TOKEN; KERBEROS_TOKEN; GSSPLUGIN_TOKEN; KRB_SVR_ENC_TOKEN; GSS_SVR_ENC_TOKEN;]
Note: All the TOKEN options in the above diagram are
available starting from Db2®
version 11.5.4.
If a value is not specified, Db2 uses the value of the authentication database manager configuration parameter.
For a description of each authentication type, see authentication - Authentication type configuration parameter
and Authentication methods for your server.
Attention: With the release of Db2
11.5.9, the CLIENT authentication type is deprecated. Do not use this authentication type
going forward, as it is insecure in many situations and might be removed in a future
release.