[
https://issues.apache.org/jira/browse/JCLOUDS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465819#comment-16465819
]
Alix Lourme commented on JCLOUDS-1414:
--------------------------------------
{quote}
Looks good to me, although I'd rather name it project-domain, as it is specific
to Keystone V3 and the "tenant" term is legacy.
{quote}
OK. Agree.
Sorry for my answer delay, but no way to use Eclipse m2 plugin with JClouds
(root cause not found) => using _eclipse:eclipse_ and let's go.
So short update on
[jclouds-site#214|https://github.com/jclouds/jclouds-site/pull/214], let's go
to code.
> OpenStack Keystone V3: Support different "domain" for "identity/user" and
> "project"
> -----------------------------------------------------------------------------------
>
> Key: JCLOUDS-1414
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1414
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
> Affects Versions: 2.1.0
> Reporter: Alix Lourme
> Priority: Minor
> Labels: keystone, openstack
>
> The [OpenStack KeyStone
> V3|https://jclouds.apache.org/blog/2018/01/16/keystone-v3/] is great, but
> fails when OpenStack platform in endpoint requires a _identify/user_ *domain*
> different than _project_ *domain.*
> Consider this required content for https://[host]/v3/auth/tokens endpoint:
> {code}
> {
> "auth": {
> "identity": {
> "methods": ["password"],
> "password": {
> "user": {
> "name": "foo",
> "domain": {
> "name": "ldap"
> },
> "password": "bar"
> }
> }
> },
> "scope": {
> "project": {
> "name": "myTenantName",
> "domain": {
> "name": "default"
> }
> }
> }
> }
> }
> {code}
> The
> [BaseAuthenticator|https://github.com/jclouds/jclouds/blob/f7b45341328410dea583901a31218a3588cb5aad/apis/openstack-keystone/src/main/java/org/jclouds/openstack/keystone/auth/functions/BaseAuthenticator.java#L84]
> is using always the same domain for the request :(.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
