Forum Discussion

Cirrocumulus

Jan 20, 2021

HTTPS Monitor: JSON File behind login page

Hello, we've already a https monitor that reads the contents of a json file, it looks like this: send string: GET /intern/api/v1/health/portal-status HTTP/1.1\r\nHost: host.company.com\r\n\r\n r...

Cirrocumulus

Jan 21, 2021

thank's for your answers!

first: it's basic authentication.

with tcpdump I've the problem with encryption.

with monitor logging, I can't see the corresponding Log-file

the part with double CR/LF seems interesting, but I think I've got a twisted pool/monitor config (wrong infos from developer)

Do you know IBM Webseal? That's the Application.

additional Info:

with

curl -sku monitor:password -H "Content-Type: application/json" -X GET https://isam-test-company.int/monitor/wga/widgets/health.json

I get:

{
    "operation" : "login"
}

jaikumar_f5
MVP
Jan 21, 2021
Haven't got a chance to work with that.

But in your original post, i see few differences. In your send string, the host header is "host.company.com", whereas in your curl you are sending "host.company.int", are you positive that its .com or .int. Because this is important, most servers have site binding or certain whitelist of domains.

Hope this wasn't a blunder mistake.

Reg the encryption, assuming this is a net new setup, can you have the server team run the service on http instead of https for time being, so we can troubleshoot, else you'll have to take the long route of bring the servers private key inside the box & then do a dump.

Basically you should be seeing a 401 coming from the server on 1st request, followed by F5 sending the credentials.

Or as twisted way, see if you can put 401 as your recv string to see if its working or not...
By any chance can you paste your https monitor config & the device version.