redirect always got fallback=true

Question

redirect always got fallback=true

Opened this issue a year ago · 21 comments

I use 127.0.0.1:8000 as gateway and localhost:9000 as client.
I try to login gateway and redirect http://127.0.0.1:8000/__welcome/ success.
then i go to the address http://localhost:9000/sso/test/
it always redirect http://127.0.0.1:8000/__welcome/?fallback=true

the exception is in Service f'{self.base_url}/sso/event/',
my base_url is 127.0.0.1:8000 but not client http://localhost:9000/
there's no url /sso/event/
is my setting wrong?

Answer 1 · 2023-02-01T06:25:18.000Z

Hi. You forget to attach gateway/client urls into your project(s). Please read Readme again. You need to add Django SSO urls to youproject/urls.py like it described in docs.

Answer 2 · 2023-02-01T08:13:38.000Z

yes. i'v already add urls to my projects like the described in docs. it's not work.

Answer 3 · 2023-02-01T12:09:23.000Z

Do you see anything in CLI? Library should report about errors.

Answer 4 · 2023-02-01T12:11:39.000Z

Please provide screenshot from CLI.

Answer 5 · 2023-02-02T01:09:11.000Z

gateway:

http://127.0.0.1:8000/login/ login admin OK.

client:

goto http://localhost:9000/sso/test/
it always redirect http://127.0.0.1:8000/__welcome/?fallback=true

sso/event error.

this is my client setting, and i am not defined the overrides.

Answer 6 · 2023-02-02T08:04:35.000Z

No. Overrides are optional. On the client side you must provide SSO server link, token and inject urls to service-side project from django_sso.sso_service.urls.

Answer 7 · 2023-02-02T08:07:58.000Z

SSO lib can't emit event to subordinated service because event aceptor url is not available - 404. Please show me your urls on service side.

Answer 8 · 2023-02-02T08:09:44.000Z

this is geteway urls.py:

this is client url.py:

Answer 9 · 2023-02-04T16:17:24.000Z

What is version of Django SSO are you use?
What is version of Django are you used?
Could you provide pure setup of Django's + the library (with same steps, what you do in your problematic project)?

For current i do not understand, how to occurs it.

Answer 10 · 2023-02-05T12:40:00.000Z

@yih0620 you could check against https://github.com/kakulukia/test_client to see whats different in you soo client, but the 404 response clearly said the url on the client side is not reachable, maybe the urlpatterns you showed above is being overwritten afterwards?

You could test manually opening http://localhost:9000/sso/event/ in the browser - it should tell you:
Method Not Allowed: /sso/event/
[05/Feb/2023 12:37:03] "GET /sso/event/ HTTP/1.1" 405 0
since its just accepting POST requests

Answer 11 · 2023-02-06T02:23:24.000Z

python version:3.7.4
django version: 3.2.17

I create new project today.
https://github.com/yih0620/ssoServerTest
https://github.com/yih0620/ssoClientTest

and thank you for your kind assistance!!

Answer 12 · 2023-02-06T06:00:58.000Z

@DAVIDhaker shouldn't obtain and even be called on different hosts? It looks like even is called on the sso server instead of the client. Which log are we seeing @yih0620 ?

Answer 13 · 2023-02-06T06:34:10.000Z

@kakulukia log from ssoservertest.
i development on a single machine, and i set the hosts file as

Answer 14 · 2023-02-07T02:08:31.000Z

i change SSO_ROOT = 'http://localhost:9000'
and reverse server and client ip
server at http://localhost:9000/
client at 127.0.0.1:8000
it work!
i think my Subordinated services ip set wrong before.

Answer 15 · 2023-02-11T10:54:01.000Z

@yih0620, hi! Excuse for long wait for reply. I think you solved problem on one's own. Little bit later i will try to test you project that you did published before.

Answer 16 · 2023-02-11T10:57:14.000Z

@DAVIDhaker shouldn't obtain and even be called on different hosts? It looks like even is called on the sso server instead of the client. Which log are we seeing @yih0620 ?

There is no difference in direct communication between services. Only in browser required different hostnames. If i understand you question right.

Answer 17 · 2023-02-11T15:39:13.000Z

@yih0620 v2.0.0 is ready. You should update. And checkout new feature. :)

Answer 18 · 2023-02-15T05:40:49.000Z

Watching for file changes with StatReloader
Exception in thread django-main-thread:
Traceback (most recent call last):
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\thread
ing.py", line 926, in _bootstrap_inner
self.run()
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\thread
ing.py", line 870, in run
self._target(*self._args, **self.kwargs)
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\site-p
ackages\django\utils\autoreload.py", line 64, in wrapper
fn(*args, **kwargs)
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\site-p
ackages\django\core\management\commands\runserver.py", line 110, in inner_run
autoreload.raise_last_exception()
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\site-p
ackages\django\utils\autoreload.py", line 87, in raise_last_exception
raise exception[1]
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\site-p
ackages\django\core\management_init.py", line 375, in execute
autoreload.check_errors(django.setup)()
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\site-p
ackages\django\utils\autoreload.py", line 64, in wrapper
fn(*args, **kwargs)
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\site-p
ackages\django_init.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\site-p
ackages\django\apps\registry.py", line 122, in populate
app_config.ready()
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python37\lib\site-p
ackages\django_sso\sso_gateway\apps.py", line 26, in ready
affected_models = self.sso_settings.affected_models_fields.keys()
AttributeError: 'Settings' object has no attribute 'affected_models_fields'

update to 2.0 i have this error@@
and downgrade back to 1.1.4, it work well..

Answer 19 · 2023-02-15T07:36:01.000Z

#8 << have a look at this to solve it

Answer 20 · 2023-02-19T23:43:11.000Z

sorry for put my problem here but i have this error

SSO token validation error
No connection adapters were found for '127.0.0.1:8000/sso/obtain/'
This error caused because SSO server don't know token of this service.

To solve this problem create subordinated service in SSO-server and put obtained token to SSO_TOKEN into settings.py file

in my settings file (sso_service_test)a put the token from my gateway_server like this
settings (sso_service_test1)
LOGIN_URL = '/login/'

SSO_ROOT = '127.0.0.1:8000'

SSO_TOKEN = 'kPeKnDUJg2uK4KGbCVzH4Cc342WHipLGWDp6wxooB1zFce37gpEdJWWtxxtUEshlTAruDfVHnNMnVf7rKjRBwBIgZRwOaV5S5v3D6cKObmlVrpCYBEqufu7cgYVH7e2AR'

in my server gateway add subordinate

but no working this is versions on my gateway and service exactly (both)
asgiref==3.6.0
certifi==2022.12.7
charset-normalizer==3.0.1
Django==4.1.7
django-sso==2.0.0
idna==3.4
requests==2.28.2
sqlparse==0.4.3
urllib3==1.26.14

any idea?

Answer 21 · 2023-03-05T23:53:55.000Z

Hello @CARocha. For first. Try to install v3 (released minutes ago). If problem not solved - contact me via email for speed up problem solving.