-
Notifications
You must be signed in to change notification settings - Fork 84
TypeError at /admin/login/ - 'NoneType' object is not subscriptable #443
Comments
@yeguacelestial did you ever solved this issue? I am facing the same one right now :( |
Hello @marcosalcazar, can't remember what I did tbh, but check out the redirect uris on Azure, and make sure you're setting correctly the site ids |
Thanks Carlos, I haven't been able to fix the issue yet, but this
functionality is on hold on our project for now. Maybe later I'll give it
another try, when needed.
El lun, 14 jun 2021 a las 20:31, Carlos Nava ***@***.***>)
escribió:
… Hello @marcosalcazar <https://github.com/marcosalcazar>,
can't remember what I did tbh, but check out the redirect uris on Azure,
and make sure you're setting correctly the site ids
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#443 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAL4CXSKF6HBNIKIRVHT6M3TS2GNJANCNFSM4XDOOO6Q>
.
--
Marcos Alcázar
|
@marcosalcazar I think I ended up using another library for validating the session with Microsoft. My backend was handled by django-allauth with Microsoft provider. And I was validating and sending the session tokens from my frontend (React Native). I would suggest you use that same flow, since handling all the session on Django could be a pain in the * if not done correctly. |
Facing the same issue, any updates? |
Sorry, no... I was doing some investigation on this but the project took another direction. Never found a solution, tough :( |
I fixed this use by fixing the MICROSOFT_AUTH_TENANT_ID in the settings.py file |
For my case, I do have the tenant id, but still get this error |
Hello, I hope you're having a great day.
I configured
MICROSOFT_AUTH_CLIENT_ID
,MICROSOFT_AUTH_CLIENT_SECRET
andMICROSOFT_AUTH_TENANT_ID
.However, when I access the
admin
site, this error keeps raising.The traceback:
Did anyone face this before?
Thank you in advance.
The text was updated successfully, but these errors were encountered: