Dear Jan,

I'm passing your question to Álvaro Alonso (from the KeyRock team), as the problem seems to be there.

Summary: Jan have created custom instances of WireCloud and KeyRock and is trying to use them jointly, but is facing some problems making it work.

Currently, when a user clicks on the login button on WireCloud, the user gets redirected to the KeyRock interface:

In this step the URL contains a plain redirect_uri parameter but, after entering the credentials and login inside the KeyRock instance, the redirect_uri parameter gets encoded. I've tested it using the Mashup Portal, and this is what I get:

In my case, the encoded redirect_uri is https%3A%2F%2Fmashup.lab.fiware.org%2Fcomplete%2Ffiware%2F but in the Jan's case the redirect_uri gets encoded as https%253A%252F%252Fwirecloud.example.com%252Fcomplete%252Ffiware%252F. Seems that the redirect_uri parameter is encoded two times...

Best Regards,
Álvaro Arranz

Ok, we will take a look.

I'm sorry but we cannot reproduce the error. It is working for us under all the flow configurations.

The issue has been emailed:

• Time sent: 29/Jun/16 12:55 PM
• To: JDegenhardt@eitco.de
• with subject: *(HELP-6751) FIWARE.Request.Tech.Apps.ApplicationMashup.Security.IDM-KeyRock.Difficulties making WireCloud with KeyRock publicly available *
  

Dear Jan,

It seems the Keyrock GE owner is not able to reproduce the issue. Do you still have the same problem?

If that is the case, are you able provide more information or other examples to produce another example to help Alvaro reproduce the issue?

Thanks,

ilknur

Comment by jdegenhardt@eitco.de :

Hi Ilknur,

probably this error came from inconsitences due to upgrades of the software. So please go ahead and close this issue since it will probably not occure after a clean new setup.

Best regards
Jan

----Ursprüngliche Nachricht----
Von: Help-Desk jira-help-desk@fi-ware.org
Gesendet: Mittwoch, 29. Juni 2016 12:56
An: Degenhardt, Jan
Betreff: [FIWARE-JIRA] (HELP-6751) FIWARE.Request.Tech.Apps.ApplicationMashup.Security.IDM-KeyRock.Difficulties making WireCloud with KeyRock publicly available

Dear Jan,

It seems the Keyrock GE owner is not able to reproduce the issue. Do you still have the same problem?

If that is the case, are you able provide more information or other examples to produce another example to help Alvaro reproduce the issue?

Thanks,

ilknur

-------------------------------------------------------------------------------
ilknur chulani created HELP-6751:
------------------------------------

Summary: FIWARE.Request.Tech.Apps.ApplicationMashup.Security.IDM-KeyRock.Difficulties making WireCloud with KeyRock publicly available
Key: HELP-6751
URL: https://jira.fiware.org/browse/HELP-6751
Project: Help-Desk
Issue Type: extRequest
Components: FIWARE-TECH-HELP
Reporter: Álvaro Arranz
Assignee: Alvaro Alonso
Priority: Critical

Dear Alvaro,

I am the FIWARE coach for the FINISH accelerator. One of the SMEs is requesting further help for this stackoverflow posting:
http://stackoverflow.com/questions/37164185/wirecloud-and-horizon-behind-https-proxy

I re-opened the associated JIRA ticket, but it seems the backlog manager closed it automatically:
https://jira.fiware.org/browse/HELP-6580

Could you kindly take a look at the issue in stackoverflow and see if you could help?

Many thanks for your help,

ilknur

-------------------------------------------------------------
Fiware-finish-coaching mailing list
Fiware-finish-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-finish-coaching
[Created via e-mail received from: "Degenhardt, Jan" <JDegenhardt@eitco.de>]

-------------------------------------------------------------------------------
Comments:

Álvaro Arranz - 10/Jun/16 10:41 AM

Dear Jan,

I'm passing your question to Álvaro Alonso (from the KeyRock team), as the problem seems to be there.

Summary: Jan have created custom instances of WireCloud and KeyRock and is trying to use them jointly, but is facing some problems making it work.

Currently, when a user clicks on the login button on WireCloud, the user gets redirected to the KeyRock interface:

In this step the URL contains a plain redirect_uri parameter but, after entering the credentials and login inside the KeyRock instance, the redirect_uri parameter gets encoded. I've tested it using the Mashup Portal, and this is what I get:

In my case, the encoded redirect_uri is https%3A%2F%2Fmashup.lab.fiware.org%2Fcomplete%2Ffiware%2F but in the Jan's case the redirect_uri gets encoded as https%253A%252F%252Fwirecloud.example.com%252Fcomplete%252Ffiware%252F. Seems that the redirect_uri parameter is encoded two times...

Best Regards,
Álvaro Arranz
------------------
Alvaro Alonso - 13/Jun/16 2:29 PM

Ok, we will take a look.

------------------
Alvaro Alonso - Friday 2:42 PM

I'm sorry but we cannot reproduce the error. It is working for us under all the flow configurations.
------------------

–

This email was generated by the JIRA Email This Issue plugin (https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.emailissue) from www.meta-inf.hu (http://www.meta-inf.hu).