Custom authentication schemes and the follow_redirects parameter

[whilenot-dev]

Version 0.28.1

Goal

I'm currently writing my own authentication scheme by subclassing the Auth class as mentioned in the docs. The requests in my authentication scheme sometimes need to follow redirects, but sometimes don't. I'd like to keep the default client behavior of following redirects, but would like to configure it on a "per-request"-basis in my Auth-subclass.

Potential issue

The follow_redirects setting is only available as parameter in the client instance and its corresponding methods to initiate a request (get, post, send etc.). Both these things are currently hidden from (A) the auth_flow-method when subclassing the Auth class, or from (B) a callable that accepts a request and returns an authenticated request instance.

Question

How is it currently possible to configure the follow_redirects parameter within a custom authentication scheme?

[KalleDK]

I have the same issue now with no real great workaround. I'm working on some custom auths, that uses other auths also. And they use redirects.

The issue is if I force follow_redirects on, then I can't intercept the redirects, but if I don't do it, then there is no good way to do the redirects myself when needed.

This also touches the fact that we don't have access to build_request from inside the auth module

I would love if we somehow could yield a RequestTmpl or something like that, that would hold the values to build_request and the follow_redirects.

[whilenot-dev]

then there is no good way to do the redirects myself when needed

For my SAP Launchpad Auth library I just duplicated the redirect behavior straight from httpx (see here) and used it in the Auth class here.

This workaround requires that follow_redirects won't ever be set by the user though.

[KalleDK]

Yeah, but my problem is that it's a general use lib, so I would like to not restrict the user :)