Hello, LRoberts, since the time I wrote my previous reply, the things have changed a bit. If you are using WCC 11.4 SP1 (and later) and Autosys 11.3.6 (and later) this has been enhanced and brings better user experience, thought not solved completely.
Because of the technical limitation of the architecture, the credentials are still being used to access the AE remote machine from WCC but they are no longer needed for running commands from Enterprise Command Line nor Forecast on that particular remote machine. This simple statement means a big change - you (i.e. administrator) can define one GLOBAL credential used for access to the AE machine. As the credential is defined as GLOBAL it is being propagated to all end users credentials and individual users doesn't need to fill any credentials - the GLOBAL one is used automatically behind the scenes. Additionally, all of the commands are being executed under the context of the WCC user - the GLOBAL credential is used only to open the remote connection to AE machine (and that is the only instance where it is needed), but not for executing of the commands from ECLI or Forecast - they are run on behalf of the user logged in to WCC.
So technically, WCC still needs non-EEM credential to access the AE machine, but it does not bother the end users, it is a single configuration step for administrator who defines this GLOBAL credential.
The only limitation here is that internal policies of your org have to allow you to have a single account for unix you can use as a GLOBAL credential.
The pre-requisities are:
- the versions (11.4 SP1+ for WCC, 11.3.6 for AE)
- AE and WCC using the same EEM (or the same failover cluster of EEM servers)
- EEM security is enabled in the AE server definition in WCC Configuration
- the AE version is properly set in the AE server definition in WCC Configuration.