[Fiware-tech-help] [Fiware-lab-help] Keyrock signup process authentication with gmail

[Enrique Garcia Navalon]

some common mistakes:
- make sure the IP is the Keystone backend one and not the Horizon one
(sometimes is the same, depends on your deployment)
- use curl o something similar to make the requests, as browsers don't
understand the raw json response from the REST API

Do a GET http://keyrock/OS-ROLES/roles/
<http://keyrock/OS-ROLES/roles/role_id> and you should have a list with, at
least, provider and purchaser role, configure local_settings.py with the
corresponding ID.
If those roles are not created, you should create them and configure
local_settings.py with the corresponding ID. If you need to create them let
me know and I can give you a script to make sure everything is correctly
set up with the permissions too.

BR,
Enrique


On Thu, 26 Nov 2015 at 14:12 zahos pap <zacpapac04 at gmail.com> wrote:

> Dear Enrique,
>
> Do you mean the http://keyrock/OS-ROLES/roles/role_id?
>
> We try the follow call
> http://51.254.200.160:8000/OS-ROLES/roles
> <http://keyrock/OS-ROLES/roles/role_id>/e2bb7a63097a4a049956c5e89ca78c7b
> with our browser (Chrome - it is GET call)
> and also to
> http://51.254.200.160:5000/OS-ROLES/roles
> <http://keyrock/OS-ROLES/roles/role_id>/e2bb7a63097a4a049956c5e89ca78c7b
>
> Both of them return error HTTP 404 not found
> Again, we have followed the default setup-configuration (The only change
> is the mail config section)
>
>
> Thanks,
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20151126/832b9364/attachment.html>