Setting necessary for allowing custom authentication/transport for http backend

[liminspace]

Setting necessary for allowing custom authentication/transport for http backend

[liminspace]

@alex-kowalczyk Is there any MJML backed that uses API Keys or OAuth2?

[alex-kowalczyk]

@liminspace I don't think that backends support that authentication directly, but it is quite common for self-hosted setups to host services behind authentication proxy, for instance with OAuth2-based JWTs in Google Cloud. Custom transport allowing to plug any authentication would be useful to integrate with such self-hosted backends.

[Alexerson]

@liminspace would you be open for a PR for this?
We are hosting the MJML function in AWS Lambda with an API Gateway and one easy way to limit access to it would be to add ApiKey Auth.
There are 2 ways I seed that could handle this use-case:

• adding a different key to the settings (like API_KEY) and simply add it to the headers in https://github.com/liminspace/django-mjml/blob/main/mjml/tools.py#L119 (but this would be maybe too specific)
• allow HTTP_AUTH to be whatever is accepted by requests, and not just a tuple.

I think the 2nd solution would be easy to implement and non-breakable. If you’re willing to consider it, I can propose a PR.

[liminspace]

@Alexerson sure, you can show your solution and I'll take it in implementing the feature

[Alexerson]

Thanks. See PR.