Page 1 of 1

HTTP WARNING: HTTP/1.1 403 Forbidden

Posted: Fri Apr 09, 2021 8:26 am
by btayl
./check_http -H awconsole.med.umich.edu -f ok -I 141.214.16.46 -u '/API/v1/mdm/devices/bulksettings' -S --sni -p 443 -a $user1$:$user2$
HTTP WARNING: HTTP/1.1 403 Forbidden - 699 bytes in 0.413 second response time |time=0.412764s;;;0.000000 size=699B;;;0

This is what I get after logging in using a wed browser

<?xml version="1.0" encoding="UTF-8"?>

-<AirWatchFaultContract xmlns="http://www.air-watch.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<ErrorCode>1013</ErrorCode>

<Message>Api tenant code header is missing.</Message>

<ActivityId>48f653ce-8db7-42d9-a700-7532d0903ee8</ActivityId>

</AirWatchFaultContract>

what do I need to do to make this work ?

Re: HTTP WARNING: HTTP/1.1 403 Forbidden

Posted: Fri Apr 09, 2021 10:09 am
by dchurch
According to my Google search, API endpoints need an aw-tenant-code HTTP header along with the request. It's only described to me as "Header value same as API key randomly generated in the AirWatch Console."

So, you'd want to get your API token from the AirWatch console, and update your command to something like this:

Code: Select all

./check_http -H x.mycompany.com -f ok -I x.x.x.x -u '/API/v1/mdm/devices/bulksettings' -S --sni -p 443 -a $user1$:$user2$ -d 'Aw-Tenant-Code: A1DEADBEEFF00'
I obfuscated IP's and host names, but you'll want to keep those the same.