[Pkg-mailman-hackers] Bug#904500: mailman3-web: OpenID account connection fails (requires ?next=)
Stephen Paul Weber
singpolyma at singpolyma.net
Tue Jul 24 22:11:00 BST 2018
Package: mailman3-web
Version: 0+20170523-14~bpo9+1
Severity: normal
Dear Maintainer,
When enabling the OpenID login option, by uncommenting this line in /etc/mailman3/mailman-web.py
'allauth.socialaccount.providers.openid',
OpenID logins work for the Mailman3 web interface as expected. However, when visiting /mailman3/accounts/social/connections/ to add a second "Account Connections" I get an error after the OpenID flow completes. The error in the log is:
Verifying return_to arguments: Parameter next not in return_to URL
And, sure enough, if I visit /mailman3/accounts/social/connections/?next=/mailman3/accounts/social/connections/ everything works as expected.
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages mailman3-web depends on:
ii dbconfig-sqlite3 2.0.9~bpo9+1
ii debconf [debconf-2.0] 1.5.61
ii lsb-base 9.20161125
ii node-less 1.6.3~dfsg-2
ii python 2.7.13-2
ii python-django-hyperkitty 1.1.4-4~bpo9+2
ii python-django-postorius 1.1.2-3~bpo9+2
ii python-psycopg2 2.6.2-1
ii python-whoosh 2.7.0-2
ii ruby-sass 3.4.23-1
ii ucf 3.0036
ii uwsgi 2.0.14+20161117-3+deb9u2
ii uwsgi-plugin-python 2.0.14+20161117-3+deb9u2
Versions of packages mailman3-web recommends:
ii libapache2-mod-proxy-uwsgi 2.0.14+20161117-3+deb9u2
Versions of packages mailman3-web suggests:
ii mariadb-server-10.1 [virtual-mysql-server] 10.1.26-0+deb9u1
ii postgresql 9.6+181+deb9u2
-- Configuration Files:
/etc/mailman3/uwsgi.ini changed [not included]
-- debconf information:
* mailman3-web/superuser-mail: root at localhost
mailman3-web/pgsql/no-empty-passwords:
mailman3-web/remote/port:
* mailman3-web/configure-webserver: apache2
* mailman3-web/emailname: localhost.local
mailman3-web/pgsql/changeconf: false
mailman3-web/nginx-choice:
* mailman3-web/superuser-name: admin
mailman3-web/remote/newhost: localhost
mailman3-web/purge: false
mailman3-web/mysql/admin-user:
mailman3-web/pgsql/authmethod-admin: ident
mailman3-web/remove-error: abort
mailman3-web/upgrade-error: abort
mailman3-web/db/dbname: mailman3web
mailman3-web/pgsql/method: TCP/IP
mailman3-web/pgsql/manualconf:
mailman3-web/mysql/method: Unix socket
mailman3-web/upgrade-backup: true
* mailman3-web/dbconfig-reinstall: false
* mailman3-web/database-type: pgsql
mailman3-web/db/basepath: /var/lib/mailman3/web
* mailman3-web/django-site: singpolyma.net
* mailman3-web/dbconfig-install: true
mailman3-web/dbconfig-remove: true
mailman3-web/internal/reconfiguring: false
mailman3-web/install-error: abort
mailman3-web/internal/skip-preseed: false
* mailman3-web/remote/host: localhost
mailman3-web/missing-db-package-error: abort
mailman3-web/db/app-user: mailman3web at localhost
mailman3-web/passwords-do-not-match:
mailman3-web/pgsql/admin-user: postgres
* mailman3-web/restart-webserver: true
mailman3-web/dbconfig-upgrade: true
mailman3-web/pgsql/authmethod-user: password
More information about the Pkg-mailman-hackers
mailing list