Allow For Configuration of Redirect URI

[python-social-auth]

Allow For Configuration of Redirect URI

[raymondberg]

It's been a long time, but I believe the key was forwarding the HTTP_HOST which in Nginx looked like the following:

proxy_set_header Host $host;

And then including the protocol (because I had issues with HTTPS URIs):

SECURE_PROXY_SSL_HEADER=('HTTP_X_FORWARDED_PROTO', 'https')

I hope this helps.

[omab]

I rather keep this out of the lib, building URIs is already done properly by the different frameworks we integrate with. In the case of Django, this library uses request.build_absolute_uri(path), which relies on _get_raw_host(), this method uses the following values (in the following order):

• HTTP_X_FORWARDED_HOST
  Header that can be set by nginx (quite common practice, and I fail to see why that it's restrictive to spawn several my_portal instances)
• HTTP_HOST
  Header sent by the client, in the case of my_portal the client is the my_proxy, this value can be set by nginx as well.
• SERVER_NAME
  Environment value, you can set this in the my_portal environment values when running it.

Setting any of the values above should get you going, the good thing about the options above, is that it lets you reuse the my_portal instances and serve the same app under different hosts without any code change.

Another alternative is to override the built-in strategy and re-define the build_absolute_uri() method to use you custom value, then set the SOCIAL_AUTH_STRATEGY setting to point to your custom version.

[omab]

Closing, reopen if still relevant.

[raymondberg]

This is really good guidance. I'm going to work on it a bit and see what I can come up with. HTTPS threw a wrench in my earlier approach so I need to do some more investigating.

[goshlanguage]

@raymondberg could you outline what you ended up doing to resolve this?
I've set HTTP_X_FORWARDED_HOST from nginx, and tried the others mentioned above, but I still get this error.

[leesolway]

I am attempting to do this in a development stack using Docker. Using proxy_set_header in NGINX sets the domain correctly in the redirect_callback, however the port port is now included. I can't see a way how to include that?

[andreimarinescu]

On my side, I believe I could definitely benefit from such a feature as I'm trying to connect a React app to social-app-django and my redirect uris will definitely be different.

I'm trying to override the default strategy as mentioned in this post, however I can't seem to get it to work. I'm getting a django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.. Is there a good place I could check about the proper way of defining a custom strategy?