Curl works - MvCall fails....

[wmgilligan]

Hi all,
I am doing some testing, and using Curl and passing the parameter -u with xxxxx:yyyyy works fine.
But, sending the same info via MvCall as a header ( 'Authorization: Basic xxxxx:yyyyy' ) fails.

I have line feeds, and have tried base64 encoding and every-time "Client Authentication failed".

Any ideas?
It appears to me that curl -u is not actually the same as auth basic... is it?

[Scot - ScotsScripts.com]

I'm not sure if this will help, but here's how I make the basic authorization work. The mvcall probably doesn't mesh with what you're doing, but maybe it will give you some ideas.

<MvASSIGN NAME="l.header" VALUE="{ 'Authorization: Basic ' $ crypto_base64_encode( l.username $ ':' $ l.password ) $ asciichar(13) $ asciichar(10) }">

<MvCALL ACTION = "{ l.url }" METHOD = "RAW" CONTENT-TYPE = "application/json; charset=utf-8" FIELDS = "l.json" FLAGS = "noparse" HEADERS = "{ l.header }">

This one works for sending json to an endpoint with basic auth.

[dcarver]

Run your curl with the -v flag to see the exact headers being sent. You should be able to mimic that request with MvCALL.

[wmgilligan]

Scott - that is essentially what I am doing (and what has always worked in the past).
DC - the v flag shows that it was doing what I thought - and yes, it is Authorization Basic.

These two posts helped me fix it! I was treating the password as a variable and _not_ as an actual string.. me bad!

Thanks!