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
We have Okta auth code that worked fine in Superset 2.x and 3.x, but 4.0.0 seems to exhibit an issue I've not yet been able to trace down where an Okta log in results in a 500 for new users that would normally get created as a result of the log in.
In 2.x or 3.x, this set up creates a new User no problem if the User does not exist.
if I upgrade a 2.x or 3.x install to 4.0.0 with these users pre-existing, Okta auth works fine.
Problem is limited to 4.0.0 and a User being created via Okta handler (sso).
2024-04-24 00:01:23,602:ERROR:superset.views.base:'NoneType' object has no attribute 'is_active'
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1823, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1799, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/security/views.py", line 628, in login
if g.user is not None and g.user.is_authenticated:
File "/usr/local/lib/python3.10/site-packages/werkzeug/local.py", line 311, in __get__
obj = instance._get_current_object()
File "/usr/local/lib/python3.10/site-packages/werkzeug/local.py", line 515, in _get_current_object
return get_name(local())
File "/usr/local/lib/python3.10/site-packages/flask_login/utils.py", line 25, in <lambda>
current_user = LocalProxy(lambda: _get_user())
File "/usr/local/lib/python3.10/site-packages/flask_login/utils.py", line 370, in _get_user
current_app.login_manager._load_user()
File "/usr/local/lib/python3.10/site-packages/flask_login/login_manager.py", line 364, in _load_user
user = self._user_callback(user_id)
File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/security/manager.py", line 2158, in load_user
if user.is_active:
AttributeError: 'NoneType' object has no attribute 'is_active'
LyleScott
changed the title
4.0.0 Okta log-in results in 500: AttributeError: 'NoneType' object has no attribute 'is_active'
4.0.0 Okta log-in results in 500: AttributeError: 'NoneType' object has no attribute 'is_active' for new users
Apr 24, 2024
LyleScott
changed the title
4.0.0 Okta log-in results in 500: AttributeError: 'NoneType' object has no attribute 'is_active' for new users
4.0.0 Okta log-in results in 500 for new users: AttributeError: 'NoneType' object has no attribute 'is_active'
Apr 24, 2024
I am going to close this for now. I think this might have been a process issue with the upgrade steps we were taking. Let me close this while I spend some time on this today/tomorrow.
Yeah, I was able to track this down. User session works fine from incognito mode. I guess it has more to do with a left over session of some sort from a previous install. I was also able to repeat this issue in 3.0.x and 3.1.0.
So, no real issue other than a dirty session from a previous install.
Bug description
We have Okta auth code that worked fine in Superset 2.x and 3.x, but 4.0.0 seems to exhibit an issue I've not yet been able to trace down where an Okta log in results in a 500 for new users that would normally get created as a result of the log in.
How to reproduce the bug
Screenshots/recordings
No response
Superset version
4.0.0
Python version
3.10
Node version
Not applicable
Browser
Not applicable
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: