[HELP-5410] FIWARE.Request.Tech.Security.IDM-KeyRock.Keyrock signup process authentication with gmail - JIRA

Details

Type: extRequest
Status: Closed
Priority: Major
Resolution: Done
Fix Version/s: 2021
Component/s: FIWARE-TECH-HELP
Labels:
None

Sender Email:
zacpapac04@gmail.com
HD-Chapter:
Security
HD-Enabler:
KeyRock

Description

Enrique,

Unfortunately, we are trying to add to new user with no success.

For example, the signup process for the user *zacpapac04 *has the error as
it described in page ValueError at _sign_up_html
Also we attach for you the result in page(back from signup to init page
with error *Error: *No Role found with id: e2bb7a63097a4a049956c5e89ca78c7b
(HTTP 404))

Also we enable from the local_settings.py the next part of config

*EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'# Configure
these for your outgoing email hostEMAIL_HOST = 'localhost'EMAIL_PORT =
25#EMAIL_HOST_USER = ''#EMAIL_HOST_PASSWORD = ''*
Any suggestions,

Best Regards,
Zacharias,
BeeZon IoT Solutions,

On Wed, Nov 25, 2015 at 5:56 PM, Enrique Garcia Navalon <
garcianavalon@gmail.com> wrote:

> Hi Zahos,
>
> The email sending uses Django's email module. The documentation here
> should cover all your questions
> https://docs.djangoproject.com/en/1.8/topics/email/#smtp-backend
>
> If you still find any problems let me know.
>
> Best regards,
> Enrique
>
>
> On Wed, 25 Nov 2015 at 16:52 zahos pap <zacpapac04@gmail.com> wrote:
>
>> Hi Again Enrique,
>>
>> First of all we would like to thank you about the significant help in our
>> last issues about keyrock, and PiraeusN node performance.
>>
>> We have deployed the IDM-Keyrock in our lab (outside the FILAB) with no
>> problem.
>> Also we deployed an sending email application Postfix (very easily!) and
>> we got emails (gmail account).
>>
>> We would like to set the Keyrock to send email (used to sign-up process
>> and forget password)
>>
>> In setting.py and according to documentation we must unquote the next
>> lines
>>
>>
>>
>>
>>
>>
>>
>> *#EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'#
>> Configure these for your outgoing email host# EMAIL_HOST =
>> 'smtp.my-company.com <http://smtp.my-company.com>'# EMAIL_PORT = 25#
>> EMAIL_HOST_USER = 'djangomail'# EMAIL_HOST_PASSWORD = 'top-secret!'*
>>
>> to
>>
>>
>>
>>
>>
>> *# Configure these for your outgoing email host#EMAIL_HOST =
>> 'mail.beezon.gr <http://mail.beezon.gr>'#EMAIL_PORT = 25#EMAIL_HOST_USER =
>> ''?'#EMAIL_HOST_PASSWORD = '?*
>>
>> The question is in the user credential area what user and password values
>> we have to set?
>> The credentials of logged in user? (We are using the logged-in user with
>> admin privileges (root) and we can not connect to Postfix to send email)
>>
>>
>> Thanks at all,
>>
>> Zacharias,
>> BeeZon IoT Solution
>>
>>
>>
>>
>>
>>
>>
>

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: zahos pap <zacpapac04@gmail.com>]

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

local_settings.py

26/Nov/15 10:51 AM

20 kB

FW External User
SignUp_Error.rar

25/Nov/15 7:29 PM

131 kB

FW External User

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Giuseppe Cossu added a comment - 26/Nov/15 8:54 AM

Hi,
I've forwarded the ticket to the GE owner, but I suppose Enrique can
continue helping you.

Regards,
Giuseppe

Show

Giuseppe Cossu added a comment - 26/Nov/15 8:54 AM Hi, I've forwarded the ticket to the GE owner, but I suppose Enrique can continue helping you. Regards, Giuseppe Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one. _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-help

Hide

Permalink

FW External User added a comment - 26/Nov/15 10:29 AM

In local_settings.py you should have a role configured under
e2bb7a63097a4a049956c5e89ca78c7b id. Make sure that role exists in Keystone
(which doesn't look like since you are getting a 404) Try fixing taht and
see if ther egistration works.

BR,
Enrique

On Thu, 26 Nov 2015 at 08:52 Giuseppe Cossu <giuseppe.cossu@create-net.org>

Show

FW External User added a comment - 26/Nov/15 10:29 AM In local_settings.py you should have a role configured under e2bb7a63097a4a049956c5e89ca78c7b id. Make sure that role exists in Keystone (which doesn't look like since you are getting a 404) Try fixing taht and see if ther egistration works. BR, Enrique On Thu, 26 Nov 2015 at 08:52 Giuseppe Cossu <giuseppe.cossu@create-net.org> Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one. _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-help

Hide

Permalink

FW External User added a comment - 26/Nov/15 10:51 AM

Yes, the file local_settings.py contains the role as

Default FIWARE roles
FIWARE_PURCHASER_ROLE_ID = 'e2bb7a63097a4a049956c5e89ca78c7b'
FIWARE_PROVIDER_ROLE_ID = 'c8205243d642482587d4a9f8ad2a1de2'

On Thu, Nov 26, 2015 at 11:27 AM, Enrique Garcia Navalon <

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help

Show

FW External User added a comment - 26/Nov/15 10:51 AM Yes, the file local_settings.py contains the role as Default FIWARE roles FIWARE_PURCHASER_ROLE_ID = 'e2bb7a63097a4a049956c5e89ca78c7b' FIWARE_PROVIDER_ROLE_ID = 'c8205243d642482587d4a9f8ad2a1de2' On Thu, Nov 26, 2015 at 11:27 AM, Enrique Garcia Navalon < Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one. _______________________________________________ Fiware-tech-help mailing list Fiware-tech-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-tech-help

Hide

Permalink

FW External User added a comment - 26/Nov/15 10:54 AM

Make sure those roles exist. You can use this call
http://docs.keyrock.apiary.io/#reference/keystone-extensions/rol/read-role-details

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help

Show

FW External User added a comment - 26/Nov/15 10:54 AM Make sure those roles exist. You can use this call http://docs.keyrock.apiary.io/#reference/keystone-extensions/rol/read-role-details Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one. _______________________________________________ Fiware-tech-help mailing list Fiware-tech-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-tech-help

Hide

Permalink

FW External User added a comment - 26/Nov/15 2:14 PM

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,

Show

FW External User added a comment - 26/Nov/15 2:14 PM 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, Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.

Hide

Permalink

FW External User added a comment - 26/Nov/15 2:28 PM

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

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help

Show

FW External User added a comment - 26/Nov/15 2:28 PM 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 Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one. _______________________________________________ Fiware-tech-help mailing list Fiware-tech-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-tech-help

People

Assignee:

Alvaro Alonso

Reporter:

FW External User

Votes:

0 Vote for this issue

Watchers:

2 Start watching this issue

Dates

Created:

25/Nov/15 7:29 PM

Updated:

27/May/21 10:58 AM

Resolved:

26/Nov/15 10:48 AM

Agile

View on Board