Liberty Collective security must support SAF keyrings and certificates that SSA will furnish, with no requirements for Subje

RFE REQUIREMENT 1:
DESCRIPTION: Collective security requires certificates and keystores outside the scope of the configuration specified by the server.xml. The certificates require specific Subject Distinguished Name (DN) values as a way to communicate authentication and authorization information between the Collective Controller and members. Multiple signing authorities are used to enable trust between the controller and members while disabling trust between members and other members. SSA policy is that SAF (Computer Associates Top Secret) certificates and keyrings must be used for servers on z/OS. SSA certificates are issued by the Federal PKI, a third-party certificate authority (CA). When certificates are issued by a third-party CA, the Subject DN values are ultimately not under the control of the certificate requester. The Subject DN in the certificate request might be used, or it might be replaced by the CA with a Subject DN format chosen by the CA. So even if Liberty Collective security supports SAF keyrings, SSA can't guarantee that the certificates produced by its mandated PKI will contain the information required for Collective security to function. SSA also can't guarantee that multiple Federal PKI CA certs are available to implement the trust model.
Liberty Collective security must support whatever SAF keyrings and certificates SSA furnishes, with no requirements for Subject Distinguished Name formats .