Network Management

 View Only

Can't get REST api operational on Aruba OS (16.11) switches for ANSIBLE use (arubaoss collection)

This thread has been viewed 3 times
  • 1.  Can't get REST api operational on Aruba OS (16.11) switches for ANSIBLE use (arubaoss collection)

    Posted May 24, 2024 07:26 AM

    Hello all

    I can't get REST API to work on any of the Aruba OS switches we've got (16.11.xxxx / 2530 & 2930)

    The typical configurations would look something like that 

    Version 1:

    aaa server-group radius "SV-Radius" host x.x.x.x

    aaa accounting rest-uri stop-only tacacs
    aaa authorization group "ansible" uri-seq 23 match-uri "v6/aaa" match-json
     "authentication" uri-access get permit
    aaa authorization rest-uri tacacs

    aaa authentication login privilege-mode

    aaa authentication rest login tacacs
    aaa authentication rest enable tacacs

    aaa authentication web login radius server-group "SV-Radius" local
    aaa authentication web enable radius server-group "SV-Radius" local
    aaa authentication ssh login radius server-group "SV-Radius" local
    aaa authentication ssh enable radius server-group "SV-Radius" local
    aaa authentication rest login radius server-group "SV-Radius" local
    aaa authentication rest enable radius server-group "SV-Radius" local

    ----------------------------------------------------------------------------------------------- 

    The point is that I get an error even before it gets to ANSIBLE:

    Http
    Invalid user name/password on the REST session; the user 'ansible' is trying to login.

    OR

    FAILED! => {"body": "{\"message\":\"Authentication failed.\"}", "changed": false, "connection": "close", "content-type": "application/json", "msg": "HTTP Error 400: Bad Request", "requestid": "", "server": "eHTTP v2.0", "status": 400, "transfer-encoding": "chunked", "url": "http://xx.xx.xx.xx:80/rest/v6.0/login-sessions"}

    How to make this work?