SP TransportOption fails to set curl username/password

[Cantor, Scott]

On 5/18/22, 4:38 AM, "users on behalf of Lukas Hämmerle via users" <users-bounces at shibboleth.net on behalf of users at shibboleth.net> wrote:

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

That's because those are the wrong numbers. Options in curl are numerically offset by various constants, and options that take strings are based at 10000 (CURLOPTTYPE_OBJECTPOINT). You add the number in the macro to get the actual option value.

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

Yes, but my point was that MDQ simply doesn't work with anything but the global options, at least if I'm remembering right. I believe it just uses the SOAP stack directly with whatever options are configured. The batch providers rely on different base classes that honor the embedded elements.

-- Scott