SP TransportOption fails to set curl username/password

[Lukas Hämmerle]

On 17.05.22 17:39, Rod Widdowson wrote:
>> or has a hint on what I'm missing here?
> 
> SWAG (from skimming the header file and the doc), try setting
> CURLOPT_HTTPAUTH (107)  to CURLAUTH_BASIC (1)

Thanks for the hint.

This did not help unfortunately. What is strange is that even though I
have now set all three options:

     <TransportOption provider="CURL" option="107">1</TransportOption>
     <TransportOption
      provider="CURL" option="173">username</TransportOption>
     <TransportOption
      provider="CURL" option="174">s3cr3tPasss0rd</TransportOption>

The log still mentions only that it could not set the latter two:

2022-05-18 08:20:39 ERROR XMLTooling.libcurl.InputStream : failed to set
CURL transport option (173)
2022-05-18 08:20:39 ERROR XMLTooling.libcurl.InputStream : failed to set
CURL transport option (174)


On 17.05.22 18:30, Cantor, Scott via users wrote:
> That seems likely. There's also the whole bit about when the global 
> TransportOption elements apply and when the ones in the metadata 
> elements apply, and I honestly don't remember which is which. I 
> vaguely seem to recall that the MDQ variant requires the global
> ones, which is obviously not likely to fly for authentication like
> this.

I would prefer not setting these curl options globally. They should be 
active only for one particular MetadataProvider.



Best Regards
Lukas


-- 
SWITCH
Lukas Hämmerle, Trust & Identity
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland
+41 44 268 15 64  lukas.haemmerle at switch.ch  http://www.switch.ch