Developer

 View Only
last person joined: 2 days ago 

Expand all | Collapse all

Authentication Issue accessing Aruba Central from AWX

This thread has been viewed 9 times
  • 1.  Authentication Issue accessing Aruba Central from AWX

    Posted Oct 07, 2022 02:58 PM

    Trying to switch from command line ansible to AWX and ran into an issue authenticating to Aruba Central.
    For native ansible command line I'm just following the example provided at https://developer.arubanetworks.com/aruba-central/docs/ansible-getting-started.

    The inventory file is defined as:

    A test playbook does the following:

    Executing the playbook works fine:

    When switching into AWX, however, I got a HTTP 401 error instead.

    The host central is defined with the exact same variables:

    Launching the exact same playbook, this is what I get: HTTP Error 401: Unauthorized.

    I tried a few tweaks including creating a custom credential type by passing ansible_httpapi_central_access_token as an environment variable, but still got the same result. I also made sure that my API token wasn't expired or anything when testing with AWX.

    Is there anything else I am missing?



  • 2.  RE: Authentication Issue accessing Aruba Central from AWX

    MVP GURU
    Posted Oct 10, 2022 04:22 AM
    What do you have when use -vvv ?

    ------------------------------
    PowerArubaSW : Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP...

    PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...)

    PowerArubaCL: Powershell Module to use Aruba Central

    PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)..

    ACEP / ACMX #107 / ACDX #1281
    ------------------------------



  • 3.  RE: Authentication Issue accessing Aruba Central from AWX

    Posted 18 days ago

    After running the AWX template with verbosity 4 and comparing it with command line ansible with -vvvv, it seems that this is triggered by AWX attempting to remove local temporary files while executing the playbook:


    The test AWX implementation I have is a container deployed on Ubuntu microk8s, I'm still trying to nail down the root cause of this.