Hi Antonio, have you checked the redirect_uri you are sending back to Keyrock as I explained in my last answer?

With respect to the support channel we use, we offer support via this channel, also via SOF and FIWARE Ask platform. You can also check the GE documentation and the online courses we offer in FIWARE Academy.

Please, don't hesitate to ask again for further help.
BR

Comment by antonio.nehme@lau.edu.lb :

Dear Alonso,

Is it possible to schedule a Skype meeting? I am planning to use the Fiware IDM component in a big project in partnership with my university and we're not making the progress required to proceed with Fiware yet.
https://www.bcubdc.com/KNP
This is what I have so far; I am receiving the authorization code but it seems like my token request's syntax is not recognized.
Moreover, I still did not manage to deploy Fiware online: I can run the Fiware instance locally and I have the database installed and functional, but cannot access this instance through the internet.
I am thankful for your help and would pretty much appreciate if we can arrange the Skype call.

Awaiting for your response.
Thank you,
Antonio

-

Dear Antonio,

The OAuth2 library used in Keyrock performs a validation of the redirect_uri parameter that comes within the token validation request, and returns the error you are encountering when that validation fails. As a result, it seems that the redirect_uri that your application is providing when redirecting the user agent to FIWARE Lab is not correct.

You can find more details about the exact validation procedure in this link.

As a side note, I myself checked that the URLs you have entered in your FIWARE Lab application (both the one of your local machine and that of the online server) are correct, so you shouldn't have to change anything there. The error seems to be in your application.

Hope this helps! Please write back if we can be of further help.

Best regards from the Keyrock team

Comment by antonio.nehme@lau.edu.lb :

Hi,

I am using an account which I have created on my local machine...
I have moved to testing Fiware OAuth:
I am running my client on my local machine; however, I am always receiving this error no matter how I change the URL.
I am calling my script on localhost:8080... you may see different combination that I have tried in the description since I also hosted the same script on an online server 'http://iago.bcu.ac.uk/anton/test/php-oauth-client/example/simple6'... However, I got the same error message...
any clue?

Your help is much appreciated,
Antonio
-

Hello,

Running the migration again shouldn't harm (you would get a DUPLICATED ENTRY error if some data already exists).

What account are you using to log in to the web portal?

BR

Comment by antonio.nehme@lau.edu.lb :

Hi,

Yes I did perform all the migrations and I am able to login to horizon portal...
Should I run $ sudo tools/with_venv.sh bin/keystone-manage -v db_sync --populate again just to be sure?

Thanks,
Antonio
-

Hello again,

Did you perform all the database migrations when installing Keystone? Especially the one that populates the database:

$ sudo tools/with_venv.sh bin/keystone-manage -v db_sync --populate

Besides, that error usually is caused by Horizon not correctly connecting to Keystone. Are you being able to log in to the web portal or you get the same error when trying to do so?

BR

Comment by antonio.nehme@lau.edu.lb :

Hi,

Thanks a lot for the previous help.
I am trying to create an application in fiware lab and I'm receiving the error shown in the attached picture. Can you please advise?

Thanks,
Antonio

-

Hello Antonio,

To be able to log in after sign up, you need to activate your account (note that the Keystone console is showing the trace "User is disabled"). To do so, you need to follow the link it is sent by email right after sign up. By default, Django outputs emails to the console, so you may find the activation link there (I can actually see some of its HTML code in the Horizon console). Please note that this email backend is fine for a development environment, but we recommend to use Postfix for a production environment. Although you already installed it, please make sure that the EMAIL_BACKEND setting is properly configured. Refer to the docs again if you have further doubts regarding email configuration.

Regarding the deployment on the cloud, could you provide more details about the problem you are running into? A configuration file like the one we provide in our Configure Apache Guide should work, and I see yours is actually pretty similar.

Hope this helps!

Regards

Comment by antonio.nehme@lau.edu.lb :

Hi,

Thanks for getting back to me; I traced the code and found that the problem was only when I check the 'I want to be a trial user' checkbox...
I have a different problem now: when I sign up, I cannot login with the same credentials. Please see the attached screenshot.

Also, I still do not know how to deploy the product on the cloud: Please check the screenshot of the configuration sent in the previous email.

Your cooperation is much appreciated.

Thanks,
Antonio

-

Hi Antonio, could you take a look to the Horizon and Keystone logs and share the error you are getting?

Thanks