Automic Workload Automation

  • Private Community
 View Only

  • 1.  User API tokens fail with 401 across clients when names share the same leading text

    Posted 16 days ago

    Hi There, 

    Environment

    • Automation Engine 24.4, REST API v1
    • Personal User Tokens (Authorization: Bearer <GUID>)
    • Two clients on the same system (e.g. 1000 and 2000)

    Summary
    For a single user, a token created in client 2000 returns HTTP 401 (code 45254) if its name shares the same leading text as a token I already have in client 1000. Only one of the two validates - the other fails. IMO, Tokens are supposed to be per-client, so identical names in different clients shouldn't interfere.

    Steps to reproduce

    1. User X creates MYTOKEN1 in client 1000 → works (200).
    2. Same user creates MYTOKEN2 in client 2000.
    3. curl -k -H "Authorization: Bearer <TOKEN>" https://<host>/ae/api/v1/2000/system/health → 401, code 45254.

    Observed: ALPHA1/ALPHA2 and ALPHA/ALPHA collide; names that differ at the start (e.g. 1000ALPHA/2000ALPHA) both work.

    Is this expected?

    Workaround: make token names differ up front (eg. lead with the client number). 



    ------------------------------
    Regards,
    Arun Verma
    ------------------------------


  • 2.  RE: User API tokens fail with 401 across clients when names share the same leading text

    Broadcom Employee
    Posted 15 days ago

    Hi @Arun Verma

    please get in contact with our Support and open a ticket with all the relevant data (version, database, log-files etc.).
    https://support.broadcom.com/

    Michael



    ------------------------------
    Michael K. Dolinek

    Engineering Program Manager | Agile Operation Division
    Broadcom Software
    ------------------------------



  • 3.  RE: User API tokens fail with 401 across clients when names share the same leading text

    Posted 13 days ago

    Hello all,

    We´ve created a ticket its Case 36987439

    Regards
    Josef 


    Original Message


  • 4.  RE: User API tokens fail with 401 across clients when names share the same leading text

    Broadcom Employee
    Posted 12 days ago

    Hi,

    this will be fixed with the next Service Pack 24.4.5:
    https://knowledge.broadcom.com/external/article?articleNumber=443808 

    Regards, Markus


    Original Message


  • 5.  RE: User API tokens fail with 401 across clients when names share the same leading text

    Posted 12 days ago

    Hi Markus,

    Thanks for letting us know. 

    Regards

    Josef 


    Original Message