Hi Javier,
may you help an INCENSE SME in using the NGSI-Source widget?

Regards,
P.

Hi, any news on this?
An INCENSE SME is blocked on this.

Thanks in advance,
P.

assigning it to Fermin, since Javier Soriano does not answer.

Fermin, may you help this INCENSE funded SME?

Thanks in advance,
P.

From a Orion point of view the "Apparently it's working fine: I can make REST queries through a web REST Client, make entities with updateContext operation and retrieve information about them with queryContext" seems to indicate that Orion is working fine. Thus, I'm assigning to Alvaro Arranz (from Wirecloud team), so he can research on this or assign to another people.

Hi Lino, Hi Pasquale,

that error code means that current logged user has no IdM credentials. This
can happens because the user is not logged using the IdM, it can be an
anonymous user (so not logged at all) or simply that the WireCloud instance
has not be configured to use the IdM. Seems you are using a custom instance
of the orion context broker, so probably that instance don't requires
authentication at all, so I recommend you to uncheck the "Use the FIWARE
credentials of the user" preference of the NGSI source operator.

Best regards,
Álvaro

On 24 July 2015 at 03:30, Fermín Galán (JIRA) <
coaches-help-desk-jira@fi-ware.org> wrote:

>
> [
> https://jira.fiware.org/browse/HELC-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Fermín Galán reassigned HELC-889:
> ---------------------------------
>
> Assignee: Álvaro Arranz (was: Fermín Galán)
>
> > Re: [Fiware-incense-coaching] queryContext from wirecloud to local orion
> contextbroker instance
> >
> -----------------------------------------------------------------------------------------------
> >
> > Key: HELC-889
> > URL: https://jira.fiware.org/browse/HELC-889
> > Project: Help-Coaches-Desk
> > Issue Type: extRequest
> > Components: INCENSe
> > Reporter: Pasquale Andriani
> > Assignee: Álvaro Arranz
> >
> > Hi Lino, I'm forwarding your request to
> > fiware-incense-coaching@lists.fi-ware.org .
> fiware-coaches@lists.fi-ware.org
> > exists for other purposes.
> > Kind regards,
> > P.
> > Pasquale Andriani
> > Direzione Ricerca e Innovazione - Research & Development Lab
> > pasquale.andriani@eng.it
> > Engineering Ingegneria Informatica spa
> > Via Riccardo Morandi, 32 - 00148 Roma
> > Tel. +39-06.87594138
> > Mob. +39 3924698746
> > Fax. +39-06.83074408
> > www.eng.it
> > On Tue, Jul 14, 2015 at 11:21 AM, Lino Prunella - Tera srl <
> > nicola.prunella@terasrl.it> wrote:
> > > Hi.
> > >
> > > I have a running instance of the Orion Context Broker GE in a CentOS
> 6.6
> > > server. Apparently it's working fine: I can make REST queries through
> a web
> > > REST Client, make entities with updateContext operation and retrieve
> > > information about them with queryContext.
> > >
> > >
> > >
> > > The thing is that I am trying to link Wirecloud GE with my Orion
> instance
> > > using the NGSI-Source widget. I have updated the widget's settings
> with my
> > > instance URL as follows:
> > >
> > >
> > >
> > > NGSI Server : http://my_ip:1026 where my_ip=192.168.1.24
> > >
> > >
> > >
> > > Entity Id Filter: Room*
> > >
> > >
> > >
> > > Ngsi-proxy is up and running on port 3000
> > >
> > >
> > >
> > > The wirecloud_instance is up and running and it shows on screen :
> > >
> > >
> > >
> > > "POST /cdp/http/192.168.1.24:1026/ngsi10/queryContext? HTTP/1.1" 422
> 42
> > >
> > >
> > >
> > > in meanwhile on my WIRECLOUD app : Fail querying the server:
> > > InvalidResponse: Unexpected error code: 422
> > >
> > >
> > >
> > > I have also deactivated the firewall and checked the port 3000.
> > >
> > >
> > >
> > > Thank you
> > >
> > >
> > >
> > > Best regards
> > >
> > >
> > >
> > > Lino Prunella
> > >
> > > Software engineering
> > >
> > > Tera srl
> > >
> > _______________________________________________
> > Fiware-incense-coaching mailing list
> > Fiware-incense-coaching@lists.fi-ware.org
> > https://lists.fi-ware.org/listinfo/fiware-incense-coaching
>
>
>
> –
> This message was sent by Atlassian JIRA
> (v6.4.1#64016)
>

Hi Lino,

I'm not sure if unchecking the "Use the FIWARE credentials of the user"
preference has solved your problems or not. If you continue having
problems, please send me the log of the operator:

[image: Inline images 1]

and if available, the body of the error response.

Best regards,
Álvaro

On 24 July 2015 at 09:29, Lino Prunella - Tera srl <
nicola.prunella@terasrl.it> wrote:

> Hi Alvaro,
>
> in my application i unchecked the "Use the FIWARE credentials of the
> user" preference of the NGSI source operator, infact wirecloud could send
> and create the relative subscription to context broker, i check this on
> wirecloud_instance and also in orion context broker log file.
>
> I’m using a custom istance instance of the orion context broker and that
> instance don't requires authentication at all.
>
>
>
> Best regards
>
>
>
> Lino Prunella
>
>
>
>
>
> Da: aarranz@conwet.com aarranz@conwet.com *Per conto di *Álvaro
> Arranz
> Inviato: venerdì 24 luglio 2015 04:08
> A: Fermín Galán (JIRA) <coaches-help-desk-jira@fi-ware.org>; Lino
> Prunella - Tera srl <nicola.prunella@terasrl.it>
> Oggetto: Re: [FI-WARE-JIRA] (HELC-889) Re: [Fiware-incense-coaching]
> queryContext from wirecloud to local orion contextbroker instance
>
>
>
> Hi Lino, Hi Pasquale,
>
>
>
> that error code means that current logged user has no IdM credentials.
> This can happens because the user is not logged using the IdM, it can be an
> anonymous user (so not logged at all) or simply that the WireCloud instance
> has not be configured to use the IdM. Seems you are using a custom instance
> of the orion context broker, so probably that instance don't requires
> authentication at all, so I recommend you to uncheck the "Use the FIWARE
> credentials of the user" preference of the NGSI source operator.
>
>
>
> Best regards,
>
> Álvaro
>
>
>
> On 24 July 2015 at 03:30, Fermín Galán (JIRA) <
> coaches-help-desk-jira@fi-ware.org> wrote:
>
>
> [
> https://jira.fiware.org/browse/HELC-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Fermín Galán reassigned HELC-889:
> ---------------------------------
>
> Assignee: Álvaro Arranz (was: Fermín Galán)
>
> > Re: [Fiware-incense-coaching] queryContext from wirecloud to local orion
> contextbroker instance
> >
> -----------------------------------------------------------------------------------------------
> >
> > Key: HELC-889
> > URL: https://jira.fiware.org/browse/HELC-889
> > Project: Help-Coaches-Desk
> > Issue Type: extRequest
> > Components: INCENSe
> > Reporter: Pasquale Andriani
> > Assignee: Álvaro Arranz
> >
> > Hi Lino, I'm forwarding your request to
> > fiware-incense-coaching@lists.fi-ware.org .
> fiware-coaches@lists.fi-ware.org
> > exists for other purposes.
> > Kind regards,
> > P.
> > Pasquale Andriani
> > Direzione Ricerca e Innovazione - Research & Development Lab
> > pasquale.andriani@eng.it
> > Engineering Ingegneria Informatica spa
> > Via Riccardo Morandi, 32 - 00148 Roma
> > Tel. +39-06.87594138
> > Mob. +39 3924698746
> > Fax. +39-06.83074408
> > www.eng.it
> > On Tue, Jul 14, 2015 at 11:21 AM, Lino Prunella - Tera srl <
> > nicola.prunella@terasrl.it> wrote:
> > > Hi.
> > >
> > > I have a running instance of the Orion Context Broker GE in a CentOS
> 6.6
> > > server. Apparently it's working fine: I can make REST queries through
> a web
> > > REST Client, make entities with updateContext operation and retrieve
> > > information about them with queryContext.
> > >
> > >
> > >
> > > The thing is that I am trying to link Wirecloud GE with my Orion
> instance
> > > using the NGSI-Source widget. I have updated the widget's settings
> with my
> > > instance URL as follows:
> > >
> > >
> > >
> > > NGSI Server : http://my_ip:1026 where my_ip=192.168.1.24
> > >
> > >
> > >
> > > Entity Id Filter: Room*
> > >
> > >
> > >
> > > Ngsi-proxy is up and running on port 3000
> > >
> > >
> > >
> > > The wirecloud_instance is up and running and it shows on screen :
> > >
> > >
> > >
> > > "POST /cdp/http/192.168.1.24:1026/ngsi10/queryContext? HTTP/1.1" 422
> 42
> > >
> > >
> > >
> > > in meanwhile on my WIRECLOUD app : Fail querying the server:
> > > InvalidResponse: Unexpected error code: 422
> > >
> > >
> > >
> > > I have also deactivated the firewall and checked the port 3000.
> > >
> > >
> > >
> > > Thank you
> > >
> > >
> > >
> > > Best regards
> > >
> > >
> > >
> > > Lino Prunella
> > >
> > > Software engineering
> > >
> > > Tera srl
> > >
> > _______________________________________________
> > Fiware-incense-coaching mailing list
> > Fiware-incense-coaching@lists.fi-ware.org
> > https://lists.fi-ware.org/listinfo/fiware-incense-coaching
>
>
>
> –
> This message was sent by Atlassian JIRA
> (v6.4.1#64016)
>
>
>

On 31 July 2015 at 12:35, Lino Prunella - Tera srl wrote:

Hi Alvaro, thank you very much for your help. Now, all is going well.

Best regards

Lino Prunella