An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferred_username as the identifier for third-party provider accounts. That value may be mutable and should therefore be avoided for authorization decisions. The providers are now using sub instead.

Affected: PyPI: django-allauth

An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferred_username as the identifier for third-party provider accounts. That value may be mutable and should therefore be avoided for authorization decisions. The providers are now using sub instead.

python311-django-allauth-65.16.1-2.1 on GA media

Affected: PyPI: django-allauth

An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferred_username as the identifier for third-party provider accounts. That value may be mutable and should therefore be avoided for authorization decisions. The providers are now using sub instead.

Affected: Ubuntu:18.04:LTS: django-allauth, Ubuntu:20.04:LTS: django-allauth, Ubuntu:22.04:LTS: django-allauth, Ubuntu:24.04:LTS: django-allauth, Ubuntu:25.10: django-allauth, Ubuntu:26.04:LTS: django-allauth

An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferred_username as the identifier for third-party provider accounts. That value may be mutable and should therefore be avoided for authorization decisions. The providers are now using sub instead.