Administering CA Configuration Automation › Configuring Users and Role-Based Security › CA EEM Single Sign-On Scenarios

CA EEM Single Sign-On Scenarios

CA Configuration Automation uses the existing CA EEM browser cookie and supports single sign-on when:

• The CA EEM user of the launching product used the CA EEM interface of the launching product to log in to CA EEM. CA Configuration Automation and the launching product share the CA EEM server.
• The launching product uses CA EEM APIs to authenticate to the CA EEM server silently and the launching product passes a token from CA EEM to the CA Configuration Automation Launch-in-Context URL parameter (EEM=[token]).

If CA EEM was not previously authenticated, the CA Configuration Automation Logon screen opens. CA EEM creates and uses the CA EEM browser cookie, and CA Configuration Automation does not support single sign-on.