Unable to set basic credentials while using HTTP Connector

[Claude Libois]

Thank you for your answer.  Indeed the problem is that our serveur throws a
401 instead of a 403 when no credentials are provided.
Thank you for your link which will greatly help me.
I thought that 403(forbdiden) was for a known user that hasn't the right to
access a resource while 401 was for wrong/missing credentials.
Best regards,
Claude


Le mer. 23 juin 2021 à 15:01, Cantor, Scott <cantor.2 at osu.edu> a écrit :

> On 6/23/21, 3:37 AM, "users on behalf of Claude Libois" <
> users-bounces at shibboleth.net on behalf of clibois.work at gmail.com> wrote:
>
> >    Is there something else to do to have basic authentication working
> with http connector ?
>
> No. I use the setBasicCredentialsWithScope variant, which takes more
> wiring work to set up, but it's conceptually the same internally, just
> means it uses the credentials with any host and port. Same objects are
> wired up in the end.
>
> Note that like most clients, it doesn't volunteer the credentials, it
> expects to get a 403 back to challenge it. It takes more wiring again to
> get the client to skip that, which I do for efficiency, I don't like extra
> round trips.
>
> My How To includes the wiring I use. [1]
>
> -- Scott
>
> [1]
> https://wiki.shibboleth.net/confluence/display/KB/Grouper+Integration+Example
>
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210623/a09868dd/attachment.htm>