SSO fails on addresses records with no associated account
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
In the rare cases where an email address exists in SSO without an associated account, SSO fails instead of handling the situation. This may be worth fixing in the code, or it may be only necessary to fix the database and prevent the situation from happening again.
Example failures are in 1988canistellau
Traceback (most recent call last):
File "/usr/lib/
response = callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/
resp = view_func(*args, **kwargs)
File "/usr/lib/
return view_func(*args, **kwargs)
File "/usr/lib/
return func(request, *args, **kwargs)
File "/usr/lib/
response = func(request, *args, **kwargs)
File "/usr/lib/
return self.view_
File "/usr/lib/
return fn(request, *args, **kwargs)
File "/usr/lib/
return func(request, *args, **kwargs)
File "/usr/lib/
if form.is_valid():
File "/usr/lib/
return self.is_bound and not bool(self.errors)
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
user = auth.authentica
File "/usr/lib/
user = backend.
File "/usr/lib/
if not account.is_active:
AttributeError: \'NoneType\' object has no attribute \'is_active\'
Changed in canonical-identity-provider: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Dud rows have been removed and should not reappear.