IT Process Automation

  • 1.  TLS 1.2 EEM

    Posted Apr 11, 2017 01:43 AM

    hi we just change the config in EEM to TLS 1.2 and after that users are not able to login to ITPAM which is integrated to EEM. Like to check if anyone have similar issues and how can it be resolved. thanks.



  • 2.  Re: TLS 1.2 EEM

    Posted Apr 11, 2017 07:35 AM

    This should be resolved by upgrading your JDK to 1.8. 

    JFYI, JDK 1.8 is supported from PAM 4.3 onwards.

     

    Thanks

    Vinay



  • 3.  Re: TLS 1.2 EEM
    Best Answer

    Broadcom Employee
    Posted Apr 11, 2017 09:25 AM

    If you are saying that you changed the igateway.conf file to restrict EEM iGateway to TLSv1.2 with the <secureProtocol> tag, then for Process Automation you will have to add a line to the c2osvcw.conf file at in addition to upgrading Java.

    If you are currently using a 1.7 release of Java, you must upgrade to update 95.

    If you are using a 1.8 release, do not use release update 91 or later.

    At the end of the c2oscvw.conf file, add this line:

     

    wrapper.java.additional.14=-Djdk.tls.client.protocols=TLSv1.2

    Ensure the number used is sequential to the last entry in the file. 

     

    If you are going to be restricting your network at the OS levels to only TLSv1.2, please get in contact with CA Support. There are a number of other things that must be considered, and EEM will have to be upgraded to the new release due out soon which is 12.51 CR06. I do not have an ETA for that, but it is coming very soon.

     

    ~Jenn



  • 4.  Re: TLS 1.2 EEM

    Posted Apr 13, 2017 03:38 AM

    thanks Jenn, managed to resolve my issue.