Our current OpenStack API clients authenticate with normal LDAP accounts that have been specifically granted access to the API bypassing our 2fa setup. If we intend to open up Swift or other parts of the API to clients that aren't managed by cloud vps admins we should make the API credential workflow not require manual admin action or user-like accounts with SSH access. In the OpenStack world I think that means application credentials.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | taavi | T316436 Cloud VPS Terraform support | |||
Resolved | Andrew | T319312 Open Openstack APIs to the public internet | |||
Resolved | taavi | T294195 Openstack API access credentials |
Event Timeline
Upstream docs seem to say that application credentials seem to always be linked to some regular user account. Not sure if that's a good or a bad thing.
Change 824830 had a related patch set uploaded (by Andrew Bogott; author: Andrew Bogott):
[operations/puppet@production] keystone: add restrict_password_auth flag
Change 824830 abandoned by Andrew Bogott:
[operations/puppet@production] keystone: add restrict_password_auth flag
Reason:
dropping in favor of https://gerrit.wikimedia.org/r/c/operations/puppet/+/825380
Change 826792 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/puppet@production] openstack: keystone: enable app credentials on codfw1dev
Change 826792 merged by Andrew Bogott:
[operations/puppet@production] openstack: keystone: enable app credentials on codfw1dev
Change 840121 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/puppet@production] openstack: keystone: enable app credentials everywhere
Change 840121 merged by Andrew Bogott:
[operations/puppet@production] openstack: keystone: enable app credentials everywhere
marking this one as resolved, the rest is tracked in T319312: Open Openstack APIs to the public internet