Unable to start the fiware-pep-proxy server about fiware-pep-proxy HOT 4 CLOSED

Hi,

it depends on where you have the user [email protected] created... If it is in the default domain, it should work.

BR

from fiware-pep-proxy.

Yes, if I'm not wrong by default multi-domain is disabled, but also I've tested it and the user is located in the default domain (I've get the information using the Default Scope request):

bitergia@af706c47bb48:~/fi-ware-pep-proxy$   curl -i \
>   -H "Content-Type: application/json" \
>   -d '
> { "auth": {
>     "identity": {
>       "methods": ["password"],
>       "password": {
>         "user": {
>           "name": "[email protected]",
>           "domain": { "id": "default" },
>           "password": "test"
>         }
>       }
>     }
>   }
> }' \
>   http://172.17.0.159:5000/v3/auth/tokens ;
HTTP/1.1 201 Created
X-Subject-Token: 3461d8f05b0...a64ef16f1
...

And there

bitergia@af706c47bb48:~/fi-ware-pep-proxy$ curl -s   -H "X-Auth-Token: 3461d8f05b0...a64ef16f1"   http://172.17.0.159:5000/v3/domains | python -mjson.tool
{
    "domains": [
        {
            "description": "Owns users and tenants (i.e. projects) available on Identity API v2.",
            "enabled": true,
            "id": "default",
            "links": {
                "self": "http://172.17.0.159:5000/v3/domains/default"
            },
            "name": "Default"
        }
    ],
    "links": {
        "next": null,
        "previous": null,
        "self": "http://172.17.0.159:5000/v3/domains"
    }
}

But, as I said below, the Domain Scoped one returns this one:

bitergia@af706c47bb48:~/fi-ware-pep-proxy$ curl -i \
>   -H "Content-Type: application/json" \
>   -d '
> { "auth": {
>     "identity": {
>       "methods": ["password"],
>       "password": {
>         "user": {
>           "name": "[email protected]",
>           "domain": { "id": "default" },
>           "password": "test"
>         }
>       }
>     },
>     "scope": {
>       "domain": {
>         "id": "default"
>       }
>     }
>   }
> }' \
>   http://172.17.0.159:5000/v3/auth/tokens ; echo
HTTP/1.1 401 Unauthorized
Www-Authenticate: Keystone uri="http://172.17.0.159:5000"
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 114
Date: Thu, 11 Jun 2015 16:54:13 GMT
{"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}

Regards!

from fiware-pep-proxy.

It seems that your user has not any role in the default domain.

"Get a domain-scoped token (Note that you’re going to need a role-assignment on the domain first!)"

from fiware-pep-proxy.

Hi Álvaro!

You are completely right. I was misunderstanding the concept role-assignment, and adding roles to the user0 into the application and not domain. When checked I've found that the user didn't have any domain-roles assigned:

{"links": {"self": "http://172.17.0.159:5000/v3/domains/default/users/user0/roles", "previous": null, "next": null}, "roles": []}

So I've added it as a 'member', re-launched the PEP proxy and the authentication was successful :)

You can close the issue.

Thanks for the support!

from fiware-pep-proxy.