On 1/9/22 5:57 AM, Axel Rau wrote:
Does the
mailman infocommand report what you think for REST credentials?yes. ... I used curl:
(mailman_33) [root@lists5 /usr/local/mailman3]# curl -v -u restadmin:??? http://localhost:8001/3.1/lists
- Trying 127.0.0.1:8001...
- Connected to localhost (91.216.35.42) port 8001 (#0)
- Server auth using Basic with user 'restadmin'
GET /3.1/lists HTTP/1.1 Host: localhost:8001 Authorization: Basic cmVzdGFkbWluOnc2cmtuQXpJZmVRc1o4WnlkMFpBcmNjcm55OA== User-Agent: curl/7.80.0 Accept: */*
- Mark bundle as not supporting multiuse < HTTP/1.1 401 Unauthorized < Server: gunicorn < Date: Sun, 09 Jan 2022 13:51:43 GMT < Connection: close
- Authentication problem. Ignoring this. < www-authenticate: Basic realm="mailman3-rest",charset="utf-8" < content-type: application/json < vary: Accept < content-length: 77 <
- Closing connection 0 {"title": "401 Unauthorized", "description": "REST API authorization failed“}
I see "Server: gunicorn“, does this mean, I must install gunicorn?
As you later reported, gunicorn is installed. It is installed as a dependency of Mailman core to serve as the REST server which is what's going on here. It also may or may not be used as the wsgi server for Django depending on how you configured that, but this is independent.
Anyway, the above is saying that restadmin:??? doesn't match what's
configured in Mailman core and reported by mailman info. Please check
carefully that these are the same in both mailman.cfg admin_pass and
settings MAILMAN_REST_API_PASS.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan