Security

 View Only
  • 1.  CPPM 6.11 CLI login not working

    Posted Apr 26, 2023 02:22 PM

    I am installing CPPM 6.11 in AWS. After launching the instance, I want ssh to the CLI  to complete the setup. I am unable to login with eTIPS123 password. 



    Note that I was following the same procedure with 6.10 and that worked.

    How can I troubleshoot this issue?

    Regards,

    Asem



  • 2.  RE: CPPM 6.11 CLI login not working

    Posted Apr 27, 2023 01:55 PM

    Hi Asem. since you have an IP configured wouldn't that mean you completed the initial setup already? With that, you would have set the appadmin password during that process?



    ------------------------------
    ACNSP | ACCP | ACMP | ACEP
    ------------------------------



  • 3.  RE: CPPM 6.11 CLI login not working

    Posted Apr 27, 2023 03:53 PM
    All I did was simply launch an instance using the AMI (CPPM-VM-x86_64-6.11.1.25), following instructions here 
    Public IP is assigned when the instance is launched. I was unable to login to CLI (using appadmin) or the web interface using admin/eTIPS123. Then I found this in the documentation (which worked): 
    "Log in to ClearPass using the appadmin account but with the eth0 MAC address as the default password.
    Using the eth0 MAC address as the default password for the admin and appadmin accounts during the initial launch only applies to AWS deployments. All other deployment types continue to use the standard appadmin default account credentials."





  • 4.  RE: CPPM 6.11 CLI login not working

    Posted Apr 28, 2023 07:38 PM
    Edited by mattAruba Apr 28, 2023 07:39 PM

    Starting 6.11, for AWS deployments, the default password for appadmin has been changed to the mac address of eth0

    It's called out in ClearPass 6.11.0 release notes




  • 5.  RE: CPPM 6.11 CLI login not working

    Posted Apr 30, 2023 01:52 AM


    reference



    ------------------------------
    If my post was useful accept solution and/or give kudos.
    Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
    ------------------------------