RAX provider does not support api-key based auth

Rackspace expects the name of the key to be "apiKey" and openstack is sending "access-key" which is the problem, I think.

PR here: https://github.com/juju/juju/pull/6357

We need to fully support the api-key method of auth and don't currently. Since much of the Rackspacee provider was copied from the OpenStack provider the access/secret-key auth doesn't apply.

We'll update to support api-key in a future release.

Rackspace has its own "username + apiKey" authentication that is different and special, and does not support openstack's access-key style authentication. See here: https://developer.rackspace.com/docs/cloud-identity/v2/general-api-info/authentication-info/sample-auth-req-response/#sample-request

For now we have disabled access-key as an authentication method, and we'll add support for the apiKey later.

Removing 2.1 milestone as we will not be addressing this issue in 2.1.

Rackspace provider does indeed have more than one authentication mechanism that are different from what Openstack provider supports. In addition to an already mentioned apiKey one, there is also a token one as well as the one that supports multi-factor authentication \o/
For detailed description, see https://developer.rackspace.com/docs/cloud-identity/v2/api-reference/token-operations/

In addition, even though at a first glance, it looks like both providers support userpass mechanism similarly, in reality it is different since Rackspace allows to provide optional tenantId and Openstack does not.

In other words, in order for us to support Rackspace mechanisms, we need to have a different identity implementation than what Openstack's goose library provide.

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.