Tiago Peres

For instances ``` {% load i18n %}{% blocktrans %}Hello! You're receiving this e-mail because you or someone else has requested a password for your user account. It can be safely...

That didn't work for me @pm-coelho while using jboss/keycloak latest version  Notice that `alg` is now `RS256` 

> @tiago-peres do you have the [crypto optional dependency](https://pyjwt.readthedocs.io/en/stable/installation.html#cryptographic-dependencies-optional) dependency installed? Well spotted... I don't and using `RUN pip install pyjwt[crypto]` doesn't build the image  Then tried `RUN pip...

> that looks like a missing OS dependency, make sure you have all that crypto requires installed and on $PATH you're right again... As per [the documentation](https://cryptography.io/en/latest/installation/#alpine): > sudo apk...

> As a workaround you can also configure keycloak to disable the RSA-OAEP key or use a different algorithm until it is supported. > > `Realm->Settings->Keys->rsa-enc-generated->enabled=False` yep, that's working if...

Thanks for this... Just added a small pledge too.

@wagnerdelima indeed, I've gone through that problem using Django Python Social Auth only. Seems to be linked with this issue => https://github.com/python-social-auth/social-core/issues/70

@nijel read the bug report. What I'm changing is not the Tenant, but the assumption that we use `common` in the url all the time. That's not true and leads...

The reason for using is that nomenclature is the way the `BASE_URL` is formed ``` BASE_URL = "https://{authority_host}/{tenant_id}" ``` The `{tenant_id}` is what I'd like have the possibility to change,...

can change it to `signin_url` and `SOCIAL_AUTH_AZUREAD_OAUTH2_SIGNIN_URL` if you prefer ([based on Microsoft's documentation](https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist?msclkid=ce865af7cc3f11ecb681eb3c54ebc1e1#solution-use-the-correct-sign-in-url))