WAS v8.5 > Reference > SetsAuthentication protocol support
Use this page to reference information regarding supported authentication protocols.
Authentication protocol support
Beginning with WebSphere Application Server v8.5, the WAS v8.5 servers only support the Common Secure Interoperability v2 (CSIv2) authentication protocol. Secure Authentication Service (SAS) is only supported between v6.0.x and previous version servers that have been federated in a v8.5 cell. The option to select between SAS, CSIv2, or both will only be made available in the administration console when a v6.0.x or previous release has been federated in a v8.5 cell.
In future releases, IBM will no longer ship or support the Secure Authentication Service (SAS) IIOP security protocol. It is recommended that we use the Common Secure Interoperability version 2 (CSIv2) protocol.
We can configure both protocols to work simultaneously between v6.0.x and previous version servers that have been federated in a v8.5 cell. If a server supports both protocols, it exports an interoperable object reference (IOR) containing tagged components describing the configuration for SAS and CSIv2. If a client supports both protocols, it reads tagged components for both CSIv2 and SAS. If the client and server support both protocols, CSIv2 is used. However, if the server supports SAS (for example, the server is a previous WAS release) and the client supports both protocols, the client chooses SAS for this request.
Choose a protocol using the com.ibm.CSI.protocol property on the client side and configure this protocol through the dmgr console on the server side.
We can configure both protocols to work simultaneously. If a server supports both protocols, it exports an interoperable object reference (IOR) containing tagged components describing the configuration for SAS and CSIv2. If a client supports both protocols, it reads tagged components for both CSIv2 and SAS. If the client and the server support both protocols, CSIv2 is used. However, if the server supports SAS (for example, it is a previous WAS release) and the client supports both protocols, the client chooses SAS for this request.
Related
Secure communications