Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Back to discussions
Expand all | Collapse all

Clearpass REST API Authorization - Bearer Token vs Basic Auth

This thread has been viewed 14 times

  • 1.  Clearpass REST API Authorization - Bearer Token vs Basic Auth

    Posted Feb 28, 2020 10:10 AM

    Hello!

    Project overview:  I am trying to use the REST API to create guest accounts via our service desk ticketing system.

    Where I'm at:  I have created the API user, gotten a Bearer Token, and I can create accounts perfectly fine using CURL from the command line.

    The problem:  The ticketing system only supports "Authorization: Basic <token>" not "Authorization: Bearer <token>".  It also supports username/password (but nothing more).

     

    I'd like to know if it is possible to get a basic token to use/API key, rather than a bearer token.

     

    In the meantime, I was able to finish my project using the tipsapi and xml files, but I'd like to move to the REST API since that's the direction ClearPass is moving, and I'm not sure how much longer the tipsapi will be supported.



  • 2.  RE: Clearpass REST API Authorization - Bearer Token vs Basic Auth
    Best Answer

    EMPLOYEE
    Posted Feb 28, 2020 10:58 AM

    No, we do not support Basic Auth for the REST API.