You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I tried to go to http://example.com/flower, I was properly redirected to a google OAuth page and signed in. After sign in (and whenever I tried to visit any page http://example.com/flower/.* thereafter), I was first redirected to:
Setup:
django-celery 3.0.11
flower 4.1 (development version as of 12/6/2012)
Issue
I was trying to get OAuth working properly running:
Using the setup described in this issue: #13
When I tried to go to http://example.com/flower, I was properly redirected to a google OAuth page and signed in. After sign in (and whenever I tried to visit any page http://example.com/flower/.* thereafter), I was first redirected to:
http://example.com/login
Unfortunately, the http://example.com/login automatically redirects to http://example.com when a user is logged in to example.com (due to the settings on example.com).
As a result, any attempt to view flower redirects to http://example.com.
Not sure, but it seems that when --url_prefix=flower is defined, oauth logins should redirect through:
http://example.com/flower/login instead of http://example.com/login
NOTE: The same issue appears to happen in flower 0.4.0 without --url_prefix. With the command:
OAuth logins seem to pass through:
http://example.com/login instead of the expected http://example.com:5555/login
This leads to a similar redirect path.
Thanks for looking into this. Appreciate any feedback or fixes you have.
The text was updated successfully, but these errors were encountered: