<html><head><title></title></head><body><!-- rte-version 0.2 9947551637294008b77bce25eb683dac --><div class="rte-style-maintainer" style="white-space: pre-wrap; font-size: small; font-family: 'Courier New', Courier; color: rgb(0, 0, 0);"data-color="global-default" bbg-color="default" data-bb-font-size="medium" bbg-font-size="medium" bbg-font-family="fixed-width">+1 on desiring OAuth-style tokens in Keystone. The use cases that come up here are people wanting to be able to execute jobs that use the APIs (Jenkins, Terraform, Vagrant, etc.) without having to save their personal credentials in plaintext somewhere, and also wanting to be able to associate credentials with a project instead of a specific person, so that if a person leaves or rotates their password it doesn't blow up their team's carefully crafted automation.<div><br></div><div>We can sort of work around it with LDAP service accounts as mentioned previously, but the concern around those is the lack of speedy revocability in the event of a compromise, and the service accounts could possibly be used to get to non-OpenStack places until they get shut down. One thought I had to try to keep the auth domain constrained to only OpenStack was using the EC2 API because at least that means you're not saving LDAP passwords on disk and the access keys are useless beyond that particular Keystone installation, but you run into impedance mismatches between the Nova API and AWS EC2 API, and we'd like people to use the native OpenStack APIs. (Turns out the notion of using AWS's EC2 API to talk to a private cloud is strange to people not steeped in cloudy things.)<br><div class="rte-style-maintainer" style="font-size: small; font-family: 'Courier New', Courier; color: rgb(0, 0, 0);"data-color="global-default" bbg-color="default" data-bb-font-size="medium" bbg-font-size="medium" bbg-font-family="fixed-width"><br><div class="bbg-rte-fold-content" data-header="From: openstack-dev@lists.openstack.org" data-digest="From: openstack-dev@lists.openstack.org" style=""><div class="bbg-rte-fold-summary">From: openstack-dev@lists.openstack.org </div><div>Subject: Re: [openstack-dev] [horizon][keystone] Getting Auth Token from Horizon when using Federation<br></div></div><blockquote>Hi Dolph,<br><br>On Mon, 2016-04-18 at 17:50 -0500, Dolph Mathews wrote:<br>> <br>> On Mon, Apr 18, 2016 at 11:34 AM, Martin Millnert <<a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:martin@millnert.se"data-destination="mailto:rte:bind">martin@millnert.se</a>><br>> wrote:<br>> Hi,<br>> <br>> we're deploying Liberty (soon Mitaka) with heavy reliance on<br>> the SAML2<br>> Federation system by Keystone where we're a Service Provider<br>> (SP).<br>> <br>> The problem in this situation is getting a token for direct<br>> API<br>> access.(*)<br>> <br>> There are conceptually two methods to use the CLI:<br>> 1) Modify ones (each customer -- in our case O(100)) IdP to<br>> add support<br>> for a feature called ECP(**), and then use keystoneauth with<br>> SAML2<br>> plugin,<br>> 2) Go to (for example) "Access & Security / API Access / View<br>> Credentials" in Horizon, and check out a token from there.<br>> <br>> <br>> With a default configuration, this token would only last a short<br>> period of time, so this would be incredibly repetitive (and thus<br>> tedious).<br><br>Indeed.<br><br>> So, I assume you mean some sort of long-lived API tokens?<br><br>Right.<br><br>> API tokens, including keystone's UUID, PKI, PKIZ, and Fernet tokens<br>> are all bearer tokens, so we force a short lifetime by default,<br>> because there are always multiple parties capable of compromising the<br>> integrity of a token. OAuth would be a counter example, where OAuth<br>> access tokens can (theoretically) live forever.<br><br>This does sound very interesting. As long as the end user gets something<br>useful to plug into the openstack auth libraries/APIs, we're home free<br>(modulo security considerations, etc).<br><br>> 2) isn't implemented. 1) is a complete blocker for many<br>> customers.<br>> <br>> Are there any principal and fundamental reasons why 2 is not<br>> doable?<br>> What I imagine needs to happen:<br>> A) User is authenticated (see *) in Horizon,<br>> B) User uses said authentication (token) to request another<br>> token from<br>> Keystone, which is displayed under the "API Access" tab on<br>> "Access &<br>> Security".<br>> <br>> <br>> The (token) here could be an OAuth access token.<br><br>Will look into this (also as per our discussion in Austin).<br><br>The one issue that has appeared in our continued discussions at home, is<br>the contrast against "service user accounts", that seems a relatively<br>prevalent/common among deployers today, which basically use<br>username/password as the api key credentials, e.g. the authZ of the<br>issued token:<br><br>If AdminNameless is Domain Admin in their domain, won't their OAuth<br>access token yield keystone tokens with the same authZ as they otherwise<br>have?<br><br>My presumptive answer being 'yes', brought me to the realization that,<br>if one wants to avoid going the way of "service user accounts" but still<br>reduce authZ, one would like to be able to get OAuth access tokens for a<br>specific project, with a specific role (e.g. "user", or [project-]admin)<br>and the authZ this entails. This would keep the traceability, which is<br>one of the main issues with non-personal accounts.<br><br>How feasible is this last bit?<br><br><br>In general, the primary use case is:<br> - I as a user of openstack on my personal computer retrieve a token to<br>manage openstack client operations without the need of storing my<br>Federation-username/password in local config (nor typing the password in<br>on the keyboard).<br><br>An extended use case definition of this being:<br> - I as a user of openstack can provision an automated system with these<br>credentials, that can continue to operate as an openstack client for a<br>very long time without maintenance (i.e., either token renewal or<br>VeryLongLifetime).<br><br>Best,<br>Martin<br><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a spellcheck="false"bbg-destination="mailto:rte:bind" href="mailto:OpenStack-dev-request@lists.openstack.org"data-destination="mailto:rte:bind">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br><a bbg-destination="rte:bind"spellcheck="false" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"data-destination="rte:bind">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></blockquote><br></div></div></div></body></html>