From orozier at ac-dijon.fr Fri Sep 1 10:39:15 2017 From: orozier at ac-dijon.fr (Olivier ROZIER) Date: Fri, 1 Sep 2017 16:39:15 +0200 Subject: [Apiman-user] How to change base url of the gateway endpoint Message-ID: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> Hello, I would like to know how to change the first part of the gateway endpoint. In fact, the endpoint takes this form : http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ When I try to access to this endpoint from a REST client on local host with this URL : http://localhost:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ it works fine. But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : http://172.56.56.123:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ it doesn't work. APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). Please, could you say me what file I can configure. Thank you in advance. Best regards. -- Olivier ROZIER ?quipe nationale de d?veloppement et int?gration d'applications Direction des Syst?mes d'Information DSI Rectorat de Dijon 2G rue du G?n?ral Delaborde - 21000 Dijon LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 www.ac-dijon.fr Pensez ? l'environnement avant d'imprimer ce message -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170901/87103f33/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170901/87103f33/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170901/87103f33/attachment-0003.png From eric.wittmann at redhat.com Fri Sep 1 11:56:31 2017 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Fri, 1 Sep 2017 11:56:31 -0400 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> Message-ID: When you say it "doesn't work" can you be more specific? Is the host unreachable or do you receive an error from the Apiman server? I'll assume that the host is simply unreachable and answer that. :) Marc will need to confirm, but I believe the vert.x server automatically binds to 0.0.0.0 when it starts up, so I don't think you should need to configure anything to bind to a specific network host. The only other thing I can think of is that your Ubuntu system has a firewall enabled and that you need to open port 8080 on that firewall so that external TCP requests can be made. https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html -Eric On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER wrote: > Hello, > > I would like to know how to change the first part of the gateway endpoint. > > In fact, the endpoint takes this form : > > http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ > > When I try to access to this endpoint from a REST client on local host with this URL : http://localhost:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ > > it works fine. > > But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : http://172.56.56.123:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ > > it doesn't work. > > APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). > > Please, could you say me what file I can configure. > > Thank you in advance. > > Best regards. > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > Pensez ? l'environnement avant d'imprimer ce message > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170901/4b6ad81b/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170901/4b6ad81b/attachment.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170901/4b6ad81b/attachment-0001.png From julien.gerboud at euranova.eu Sun Sep 3 10:59:55 2017 From: julien.gerboud at euranova.eu (Julien Gerboud) Date: Sun, 03 Sep 2017 14:59:55 +0000 Subject: [Apiman-user] Health Check URL for API Gateway Message-ID: Hello to you all, I am setting up a load balancer (HA Proxy) in front of 2 (or more) APIMan API Gateways. In order to know which instance is up, the load balancer needs an health check. I tried to use the /system/status/ endpoint of the gateway but I get a 500 error with a "X-Gateway-Error: Invalid endpoint provided: /system/status/" header. Is there another health check endpoint or a REST Doc for the API Gateway? I am using APIMan version 1.3.0.Final. Thanks for your help! Regards, Julien GERBOUD -- ______________________________ *Julien GERBOUD* Developer (M) +32 475 78 05 31 <+32%20475%2078%2005%2031> *EURA NOVA* Rue Emile Francqui, 4 1435 Mont-Saint-Guibert (T) +32 10 75 02 00 <+32%2010%2075%2002%2000> *euranova.eu * *research.euranova.eu* -- ? Be green, keep it on the screen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170903/02beb8c6/attachment.html From marc.savy at redhat.com Sun Sep 3 13:30:05 2017 From: marc.savy at redhat.com (Marc Savy) Date: Sun, 3 Sep 2017 18:30:05 +0100 Subject: [Apiman-user] Health Check URL for API Gateway In-Reply-To: References: Message-ID: Hi, Which version of the gateway are you using? Vert.x or Servlet? Regards, Marc On Sunday, September 3, 2017, Julien Gerboud wrote: > Hello to you all, > > I am setting up a load balancer (HA Proxy) in front of 2 (or more) APIMan > API Gateways. In order to know which instance is up, the load balancer > needs an health check. > > I tried to use the /system/status/ endpoint of the gateway but I get a 500 > error with a "X-Gateway-Error: Invalid endpoint provided: /system/status/" > header. > > Is there another health check endpoint or a REST Doc for the API Gateway? > > I am using APIMan version 1.3.0.Final. > > Thanks for your help! > > Regards, > Julien GERBOUD > -- > > ______________________________ > > *Julien GERBOUD* > > Developer > (M) +32 475 78 05 31 <+32%20475%2078%2005%2031> > > *EURA NOVA* > > Rue Emile Francqui, 4 > > 1435 Mont-Saint-Guibert > > (T) +32 10 75 02 00 <+32%2010%2075%2002%2000> > > *euranova.eu * > > *research.euranova.eu* > > ? Be green, keep it on the screen -- Sent from mobile phone, apologies for brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170903/af5c5d8c/attachment-0001.html From julien.gerboud at euranova.eu Mon Sep 4 03:50:15 2017 From: julien.gerboud at euranova.eu (Julien Gerboud) Date: Mon, 04 Sep 2017 07:50:15 +0000 Subject: [Apiman-user] Health Check URL for API Gateway In-Reply-To: References: Message-ID: Hi Marc, Thanks for your quick reaction. I am using the Servlet version. To be more precise, I am using the Wildfly10 docker image with tag 1.3.0.Final (I kept only the gateway part, the manager, elasticsearch, keycloak and database are on different containers). Regards, On Sun, 3 Sep 2017 at 19:30 Marc Savy wrote: > Hi, > > Which version of the gateway are you using? Vert.x or Servlet? > > Regards, > Marc > > > On Sunday, September 3, 2017, Julien Gerboud > wrote: > >> Hello to you all, >> >> I am setting up a load balancer (HA Proxy) in front of 2 (or more) APIMan >> API Gateways. In order to know which instance is up, the load balancer >> needs an health check. >> >> I tried to use the /system/status/ endpoint of the gateway but I get a >> 500 error with a "X-Gateway-Error: Invalid endpoint provided: >> /system/status/" header. >> >> Is there another health check endpoint or a REST Doc for the API Gateway? >> >> I am using APIMan version 1.3.0.Final. >> >> Thanks for your help! >> >> Regards, >> Julien GERBOUD >> -- >> >> ______________________________ >> >> *Julien GERBOUD* >> >> Developer >> (M) +32 475 78 05 31 <+32%20475%2078%2005%2031> >> >> *EURA NOVA* >> >> Rue Emile Francqui, 4 >> >> 1435 Mont-Saint-Guibert >> >> (T) +32 10 75 02 00 <+32%2010%2075%2002%2000> >> >> *euranova.eu * >> >> *research.euranova.eu* >> >> ? Be green, keep it on the screen > > > > -- > Sent from mobile phone, apologies for brevity. > -- ______________________________ *Julien GERBOUD* Developer (M) +32 475 78 05 31 <+32%20475%2078%2005%2031> *EURA NOVA* Rue Emile Francqui, 4 1435 Mont-Saint-Guibert (T) +32 10 75 02 00 <+32%2010%2075%2002%2000> *euranova.eu * *research.euranova.eu* -- ? Be green, keep it on the screen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/98d54f86/attachment.html From orozier at ac-dijon.fr Mon Sep 4 04:47:09 2017 From: orozier at ac-dijon.fr (Olivier ROZIER) Date: Mon, 4 Sep 2017 10:47:09 +0200 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> Message-ID: <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> Hello Eric, Thank you for your answer. In fact, when I say "it doesn't work", I would say that there is no result in the client REST but also, there is no error message. I haven't got response in fact... When I execute the command /netstat -ltanu/, I have this result : As you can see, I have got the line 127.0.0.1:8080 but I haven't got the line 169.254.107.101:8080 I think the problem comes from here but I don't know in which file I must specify the IP Address and the port (169.254.107.101:8080). Moreover, I haven't got firewall. Do you understand better? Thank you in advance for your help. Olivier Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit?: > When you say it "doesn't work" can you be more specific?? Is the host > unreachable or do you receive an error from the Apiman server? > > I'll assume that the host is simply unreachable and answer that. :) > > Marc will need to confirm, but I believe the vert.x server > automatically binds to 0.0.0.0 when it starts up, so I don't think you > should need to configure anything to bind to a specific network host. > > The only other thing I can think of is that your Ubuntu system has a > firewall enabled and that you need to open port 8080 on that firewall > so that external TCP requests can be made. > > https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html > > -Eric > > On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER > wrote: > > Hello, > > I would like to know how to change the first part of the gateway > endpoint. > > In fact, the endpoint takes this form : > > http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ > > When I try to access to this endpoint from a REST client on local host with this URL : > http://localhost:8080/apiman-gateway/ > {organizationId}/{API ID}/{API version}/ > > it works fine. > > But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : > http://172.56.56.123:8080/apiman-gateway/ > {organizationId}/{API ID}/{API version}/ > > it doesn't work. > > APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). > > Please, could you say me what file I can configure. > > Thank you in advance. > > Best regards. > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > > > Pensez ? l'environnement avant d'imprimer ce message > > > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > > > -- Olivier ROZIER ?quipe nationale de d?veloppement et int?gration d'applications Direction des Syst?mes d'Information DSI Rectorat de Dijon 2G rue du G?n?ral Delaborde - 21000 Dijon LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 www.ac-dijon.fr Pensez ? l'environnement avant d'imprimer ce message -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/8058f559/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/8058f559/attachment-0003.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/8058f559/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/8058f559/attachment-0005.png From marc.savy at redhat.com Mon Sep 4 05:37:20 2017 From: marc.savy at redhat.com (Marc Savy) Date: Mon, 4 Sep 2017 10:37:20 +0100 Subject: [Apiman-user] Health Check URL for API Gateway In-Reply-To: References: Message-ID: Julien, The standard status endpoint or the *gateway* is: http://apimanager:apiman123!@localhost:8080/apiman-gateway-api/system/status Notice the embedded default username and password (remember to substitute for whatever security mechanism you set it up) I just checked out the 1.3.0.Final image and it seems to work okay for me. You can also do the same for the apiman manager endpoint, but instead it is: http://localhost:8080/apiman/system/status Let me know if it works for you. Regards, Marc On 4 September 2017 at 08:48, Julien Gerboud wrote: > Hi Marc, > > Thanks for your quick reaction. > > I am using the Servlet version. To be more precise, I am using the Wildfly10 > docker image with tag 1.3.0.Final (I kept only the gateway part, the > manager, elasticsearch, keycloak and database are on different containers). > > Regards, > > On Sun, 3 Sep 2017 at 19:30 Marc Savy wrote: >> >> Hi, >> >> Which version of the gateway are you using? Vert.x or Servlet? >> >> Regards, >> Marc >> >> >> On Sunday, September 3, 2017, Julien Gerboud >> wrote: >>> >>> Hello to you all, >>> >>> I am setting up a load balancer (HA Proxy) in front of 2 (or more) APIMan >>> API Gateways. In order to know which instance is up, the load balancer needs >>> an health check. >>> >>> I tried to use the /system/status/ endpoint of the gateway but I get a >>> 500 error with a "X-Gateway-Error: Invalid endpoint provided: >>> /system/status/" header. >>> >>> Is there another health check endpoint or a REST Doc for the API Gateway? >>> >>> I am using APIMan version 1.3.0.Final. >>> >>> Thanks for your help! >>> >>> Regards, >>> Julien GERBOUD >>> -- >>> >>> ______________________________ >>> >>> Julien GERBOUD >>> >>> Developer >>> (M) +32 475 78 05 31 >>> >>> EURA NOVA >>> >>> Rue Emile Francqui, 4 >>> >>> 1435 Mont-Saint-Guibert >>> >>> (T) +32 10 75 02 00 >>> >>> euranova.eu >>> >>> research.euranova.eu >>> >>> >>> ? Be green, keep it on the screen >> >> >> >> -- >> Sent from mobile phone, apologies for brevity. > > -- > > ______________________________ > > Julien GERBOUD > > Developer > (M) +32 475 78 05 31 > > EURA NOVA > > Rue Emile Francqui, 4 > > 1435 Mont-Saint-Guibert > > (T) +32 10 75 02 00 > > euranova.eu > > research.euranova.eu > > > ? Be green, keep it on the screen From marc.savy at redhat.com Mon Sep 4 05:46:07 2017 From: marc.savy at redhat.com (Marc Savy) Date: Mon, 4 Sep 2017 10:46:07 +0100 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> Message-ID: Thanks for the clarification, that's helpful. I'll look into it and get back to you shortly. Regards, Marc On 4 September 2017 at 09:47, Olivier ROZIER wrote: > Hello Eric, > > Thank you for your answer. > > In fact, when I say "it doesn't work", I would say that there is no result > in the client REST but also, there is no error message. I haven't got > response in fact... > > When I execute the command *netstat -ltanu*, I have this result : > > As you can see, I have got the line 127.0.0.1:8080 but I haven't got the > line 169.254.107.101:8080 > > I think the problem comes from here but I don't know in which file I must > specify the IP Address and the port (169.254.107.101:8080). > > Moreover, I haven't got firewall. > > Do you understand better? > > Thank you in advance for your help. > > Olivier > > > > Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit : > > When you say it "doesn't work" can you be more specific? Is the host > unreachable or do you receive an error from the Apiman server? > > I'll assume that the host is simply unreachable and answer that. :) > > Marc will need to confirm, but I believe the vert.x server automatically > binds to 0.0.0.0 when it starts up, so I don't think you should need to > configure anything to bind to a specific network host. > > The only other thing I can think of is that your Ubuntu system has a > firewall enabled and that you need to open port 8080 on that firewall so > that external TCP requests can be made. > > https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html > > -Eric > > On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER > wrote: > >> Hello, >> >> I would like to know how to change the first part of the gateway endpoint. >> >> In fact, the endpoint takes this form : >> >> http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ >> >> When I try to access to this endpoint from a REST client on local host with this URL : http://localhost:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ >> >> it works fine. >> >> But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : http://172.56.56.123:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ >> >> it doesn't work. >> >> APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). >> >> Please, could you say me what file I can configure. >> >> Thank you in advance. >> >> Best regards. >> >> -- >> >> Olivier ROZIER >> ?quipe nationale de d?veloppement et int?gration d'applications >> Direction des Syst?mes d'Information >> DSI >> >> Rectorat de Dijon >> 2G rue du G?n?ral Delaborde - 21000 Dijon >> >> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >> www.ac-dijon.fr >> Pensez ? l'environnement avant d'imprimer ce message >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> >> > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > Pensez ? l'environnement avant d'imprimer ce message > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/ba079b1f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/ba079b1f/attachment-0003.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/ba079b1f/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/ba079b1f/attachment-0005.png From orozier at ac-dijon.fr Mon Sep 4 07:24:38 2017 From: orozier at ac-dijon.fr (Olivier ROZIER) Date: Mon, 4 Sep 2017 13:24:38 +0200 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> Message-ID: <7ce0f04f-93d5-0a77-0076-353e04c583bd@ac-dijon.fr> Thank you Mark ;-) Le 04/09/2017 ? 11:46, Marc Savy a ?crit?: > Thanks for the clarification, that's helpful. I'll look into it and > get back to you shortly. > > Regards, > Marc > > On 4 September 2017 at 09:47, Olivier ROZIER > wrote: > > Hello Eric, > > Thank you for your answer. > > In fact, when I say "it doesn't work", I would say that there is > no result in the client REST but also, there is no error message. > I haven't got response in fact... > > When I execute the command /netstat -ltanu/, I have this result : > > As you can see, I have got the line 127.0.0.1:8080 > but I haven't got the line > 169.254.107.101:8080 > > I think the problem comes from here but I don't know in which file > I must specify the IP Address and the port (169.254.107.101:8080 > ). > > Moreover, I haven't got firewall. > > Do you understand better? > > Thank you in advance for your help. > > Olivier > > > > Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit?: >> When you say it "doesn't work" can you be more specific?? Is the >> host unreachable or do you receive an error from the Apiman server? >> >> I'll assume that the host is simply unreachable and answer that. :) >> >> Marc will need to confirm, but I believe the vert.x server >> automatically binds to 0.0.0.0 when it starts up, so I don't >> think you should need to configure anything to bind to a specific >> network host. >> >> The only other thing I can think of is that your Ubuntu system >> has a firewall enabled and that you need to open port 8080 on >> that firewall so that external TCP requests can be made. >> >> https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html >> >> >> -Eric >> >> On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER >> > wrote: >> >> Hello, >> >> I would like to know how to change the first part of the >> gateway endpoint. >> >> In fact, the endpoint takes this form : >> >> http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ >> >> When I try to access to this endpoint from a REST client on local host with this URL : >> http://localhost:8080/apiman-gateway/ >> {organizationId}/{API ID}/{API version}/ >> >> it works fine. >> >> But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : >> http://172.56.56.123:8080/apiman-gateway/ >> {organizationId}/{API ID}/{API version}/ >> >> it doesn't work. >> >> APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). >> >> Please, could you say me what file I can configure. >> >> Thank you in advance. >> >> Best regards. >> >> -- >> >> Olivier ROZIER >> ?quipe nationale de d?veloppement et int?gration d'applications >> Direction des Syst?mes d'Information >> DSI >> >> Rectorat de Dijon >> 2G rue du G?n?ral Delaborde - 21000 Dijon >> >> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >> www.ac-dijon.fr >> >> >> Pensez ? l'environnement avant d'imprimer ce message >> >> >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> >> >> > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > > > Pensez ? l'environnement avant d'imprimer ce message > > > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > > > -- Olivier ROZIER ?quipe nationale de d?veloppement et int?gration d'applications Direction des Syst?mes d'Information DSI Rectorat de Dijon 2G rue du G?n?ral Delaborde - 21000 Dijon LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 www.ac-dijon.fr Pensez ? l'environnement avant d'imprimer ce message -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/3ff9a132/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/3ff9a132/attachment-0003.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/3ff9a132/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170904/3ff9a132/attachment-0005.png From orozier at ac-dijon.fr Tue Sep 5 02:32:17 2017 From: orozier at ac-dijon.fr (Olivier ROZIER) Date: Tue, 5 Sep 2017 08:32:17 +0200 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> Message-ID: <9b2a54c1-3663-e441-c68f-adcde170d548@ac-dijon.fr> Hello Mark, I forgot to say you that I use APIMAN 1.3.1.Final overlayfor Wildfly 10 and APIMAN 1.3.1.Final Vert.x Gateway. Thank you for your help. Olivier Le 04/09/2017 ? 11:46, Marc Savy a ?crit?: > Thanks for the clarification, that's helpful. I'll look into it and > get back to you shortly. > > Regards, > Marc > > On 4 September 2017 at 09:47, Olivier ROZIER > wrote: > > Hello Eric, > > Thank you for your answer. > > In fact, when I say "it doesn't work", I would say that there is > no result in the client REST but also, there is no error message. > I haven't got response in fact... > > When I execute the command /netstat -ltanu/, I have this result : > > As you can see, I have got the line 127.0.0.1:8080 > but I haven't got the line > 169.254.107.101:8080 > > I think the problem comes from here but I don't know in which file > I must specify the IP Address and the port (169.254.107.101:8080 > ). > > Moreover, I haven't got firewall. > > Do you understand better? > > Thank you in advance for your help. > > Olivier > > > > Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit?: >> When you say it "doesn't work" can you be more specific?? Is the >> host unreachable or do you receive an error from the Apiman server? >> >> I'll assume that the host is simply unreachable and answer that. :) >> >> Marc will need to confirm, but I believe the vert.x server >> automatically binds to 0.0.0.0 when it starts up, so I don't >> think you should need to configure anything to bind to a specific >> network host. >> >> The only other thing I can think of is that your Ubuntu system >> has a firewall enabled and that you need to open port 8080 on >> that firewall so that external TCP requests can be made. >> >> https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html >> >> >> -Eric >> >> On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER >> > wrote: >> >> Hello, >> >> I would like to know how to change the first part of the >> gateway endpoint. >> >> In fact, the endpoint takes this form : >> >> http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ >> >> When I try to access to this endpoint from a REST client on local host with this URL : >> http://localhost:8080/apiman-gateway/ >> {organizationId}/{API ID}/{API version}/ >> >> it works fine. >> >> But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : >> http://172.56.56.123:8080/apiman-gateway/ >> {organizationId}/{API ID}/{API version}/ >> >> it doesn't work. >> >> APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). >> >> Please, could you say me what file I can configure. >> >> Thank you in advance. >> >> Best regards. >> >> -- >> >> Olivier ROZIER >> ?quipe nationale de d?veloppement et int?gration d'applications >> Direction des Syst?mes d'Information >> DSI >> >> Rectorat de Dijon >> 2G rue du G?n?ral Delaborde - 21000 Dijon >> >> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >> www.ac-dijon.fr >> >> >> Pensez ? l'environnement avant d'imprimer ce message >> >> >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> >> >> > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > > > Pensez ? l'environnement avant d'imprimer ce message > > > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > > > -- Olivier ROZIER ?quipe nationale de d?veloppement et int?gration d'applications Direction des Syst?mes d'Information DSI Rectorat de Dijon 2G rue du G?n?ral Delaborde - 21000 Dijon LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 www.ac-dijon.fr Pensez ? l'environnement avant d'imprimer ce message -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/9ea3e16a/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/9ea3e16a/attachment-0003.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/9ea3e16a/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/9ea3e16a/attachment-0005.png From marc.savy at redhat.com Tue Sep 5 08:26:25 2017 From: marc.savy at redhat.com (Marc Savy) Date: Tue, 5 Sep 2017 13:26:25 +0100 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: <9b2a54c1-3663-e441-c68f-adcde170d548@ac-dijon.fr> References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> <9b2a54c1-3663-e441-c68f-adcde170d548@ac-dijon.fr> Message-ID: Hi Olivier, Does *hostname* not work for you: https://github.com/apiman/apiman/blob/master/distro/vertx/src/main/resources/overlay/configs/conf-es.json#L219 You can also alter the reported endpoint with *publicEndpoint*: https://github.com/apiman/apiman/blob/master/distro/vertx/src/main/resources/overlay/configs/conf-es.json#L223 It seems to work (on 1.3.1.Final, at least), but please verify and let us know. Regards, Marc On 5 September 2017 at 07:32, Olivier ROZIER wrote: > Hello Mark, > > I forgot to say you that I use APIMAN 1.3.1.Final overlayfor Wildfly 10 > and APIMAN 1.3.1.Final Vert.x Gateway. > > Thank you for your help. > > Olivier > > Le 04/09/2017 ? 11:46, Marc Savy a ?crit : > > Thanks for the clarification, that's helpful. I'll look into it and get > back to you shortly. > > Regards, > Marc > > On 4 September 2017 at 09:47, Olivier ROZIER wrote: > >> Hello Eric, >> >> Thank you for your answer. >> >> In fact, when I say "it doesn't work", I would say that there is no >> result in the client REST but also, there is no error message. I haven't >> got response in fact... >> >> When I execute the command *netstat -ltanu*, I have this result : >> >> As you can see, I have got the line 127.0.0.1:8080 but I haven't got the >> line 169.254.107.101:8080 >> >> I think the problem comes from here but I don't know in which file I must >> specify the IP Address and the port (169.254.107.101:8080). >> >> Moreover, I haven't got firewall. >> >> Do you understand better? >> >> Thank you in advance for your help. >> >> Olivier >> >> >> >> Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit : >> >> When you say it "doesn't work" can you be more specific? Is the host >> unreachable or do you receive an error from the Apiman server? >> >> I'll assume that the host is simply unreachable and answer that. :) >> >> Marc will need to confirm, but I believe the vert.x server automatically >> binds to 0.0.0.0 when it starts up, so I don't think you should need to >> configure anything to bind to a specific network host. >> >> The only other thing I can think of is that your Ubuntu system has a >> firewall enabled and that you need to open port 8080 on that firewall so >> that external TCP requests can be made. >> >> https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html >> >> -Eric >> >> On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER >> wrote: >> >>> Hello, >>> >>> I would like to know how to change the first part of the gateway >>> endpoint. >>> >>> In fact, the endpoint takes this form : >>> >>> http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>> >>> When I try to access to this endpoint from a REST client on local host with this URL : http://localhost:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>> >>> it works fine. >>> >>> But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : http://172.56.56.123:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>> >>> it doesn't work. >>> >>> APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). >>> >>> Please, could you say me what file I can configure. >>> >>> Thank you in advance. >>> >>> Best regards. >>> >>> -- >>> >>> Olivier ROZIER >>> ?quipe nationale de d?veloppement et int?gration d'applications >>> Direction des Syst?mes d'Information >>> DSI >>> >>> Rectorat de Dijon >>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>> >>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>> www.ac-dijon.fr >>> Pensez ? l'environnement avant d'imprimer ce message >>> >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>> >>> >> >> -- >> >> Olivier ROZIER >> ?quipe nationale de d?veloppement et int?gration d'applications >> Direction des Syst?mes d'Information >> DSI >> >> Rectorat de Dijon >> 2G rue du G?n?ral Delaborde - 21000 Dijon >> >> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >> www.ac-dijon.fr >> Pensez ? l'environnement avant d'imprimer ce message >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> >> > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > Pensez ? l'environnement avant d'imprimer ce message > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/8c7c5b25/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/8c7c5b25/attachment-0003.png -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/8c7c5b25/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/8c7c5b25/attachment-0005.png From orozier at ac-dijon.fr Tue Sep 5 10:28:06 2017 From: orozier at ac-dijon.fr (Olivier ROZIER) Date: Tue, 5 Sep 2017 16:28:06 +0200 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> <9b2a54c1-3663-e441-c68f-adcde170d548@ac-dijon.fr> Message-ID: <29fb6bd3-a8c0-7980-49cc-e77e667e9182@ac-dijon.fr> Hi Marc, I think I did something wrong and I don't configure the right file "conf-es.json" because nothing happened. When I install APIMAN, I followed these instructions : http://www.apiman.io/latest/download.html Then, I created the API Implementation and I choose the Vert.x gateway in the list (there is also the default gateway which also exists)? as you can see below : 1) I have tried to change *hostname* and *publicEndpoint* in the file "apiman-1.3.1.Final/apiman-distro-verts-1.3.1.Final/configs/conf-es.json". 2) Then I restart APIMAN from the directory "apiman-1.3.1.Final/wildfly-10.1.0.Final" with the command : /./bin/standalone.sh -c standalone-apiman.xml/ 3) Then I restart the gateway from the directory "apiman-distro-vertx-1.3.1.Final" with the command /./apiman-gateway.sh --conf=configs/conf-es.json /but the result is the same in the REST client. When I write this URL : I have this result : but when I try with the URL http://169.254.107.101:8080/apiman-gateway/Organisationfournisseurdese...... I have this result : And in the response headers, there is nothing at all. Nevertheless, I'm on the host where APIMAN is installed. When I try a telnet with the IP address on the port 8080, it doesn't work but when I try with "localhost", it connects. However, it the same host. I think something is wrong on my host because even if I don't start the Vert.x gateway with the command "/./apiman-gateway.sh --conf=configs/conf-es.json/" and I only start APIMAN, I get the good response in the REST client with "localhost" in the URL. Is it normal that there is no need to start the Vert.x gateway to the REST client return the good response? Thank you for your help. Olivier Le 05/09/2017 ? 14:26, Marc Savy a ?crit?: > Hi Olivier, > > Does *hostname* not work for you: > > https://github.com/apiman/apiman/blob/master/distro/vertx/src/main/resources/overlay/configs/conf-es.json#L219 > > You can also alter the reported endpoint with *publicEndpoint*: > > https://github.com/apiman/apiman/blob/master/distro/vertx/src/main/resources/overlay/configs/conf-es.json#L223 > > It seems to work (on 1.3.1.Final, at least), but please verify and let > us know. > > Regards, > Marc > > On 5 September 2017 at 07:32, Olivier ROZIER > wrote: > > Hello Mark, > > I forgot to say you that I use APIMAN 1.3.1.Final overlayfor > Wildfly 10 and APIMAN 1.3.1.Final Vert.x Gateway. > > Thank you for your help. > > Olivier > > > Le 04/09/2017 ? 11:46, Marc Savy a ?crit?: >> Thanks for the clarification, that's helpful. I'll look into it >> and get back to you shortly. >> >> Regards, >> Marc >> >> On 4 September 2017 at 09:47, Olivier ROZIER > > wrote: >> >> Hello Eric, >> >> Thank you for your answer. >> >> In fact, when I say "it doesn't work", I would say that there >> is no result in the client REST but also, there is no error >> message. I haven't got response in fact... >> >> When I execute the command /netstat -ltanu/, I have this result : >> >> As you can see, I have got the line 127.0.0.1:8080 >> but I haven't got the line >> 169.254.107.101:8080 >> >> I think the problem comes from here but I don't know in which >> file I must specify the IP Address and the port >> (169.254.107.101:8080 ). >> >> Moreover, I haven't got firewall. >> >> Do you understand better? >> >> Thank you in advance for your help. >> >> Olivier >> >> >> >> Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit?: >>> When you say it "doesn't work" can you be more specific?? Is >>> the host unreachable or do you receive an error from the >>> Apiman server? >>> >>> I'll assume that the host is simply unreachable and answer >>> that. :) >>> >>> Marc will need to confirm, but I believe the vert.x server >>> automatically binds to 0.0.0.0 when it starts up, so I don't >>> think you should need to configure anything to bind to a >>> specific network host. >>> >>> The only other thing I can think of is that your Ubuntu >>> system has a firewall enabled and that you need to open port >>> 8080 on that firewall so that external TCP requests can be made. >>> >>> https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html >>> >>> >>> -Eric >>> >>> On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER >>> > wrote: >>> >>> Hello, >>> >>> I would like to know how to change the first part of the >>> gateway endpoint. >>> >>> In fact, the endpoint takes this form : >>> >>> http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>> >>> When I try to access to this endpoint from a REST client on local host with this URL : >>> http://localhost:8080/apiman-gateway/ >>> {organizationId}/{API ID}/{API version}/ >>> >>> it works fine. >>> >>> But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : >>> http://172.56.56.123:8080/apiman-gateway/ >>> {organizationId}/{API ID}/{API version}/ >>> >>> it doesn't work. >>> >>> APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). >>> >>> Please, could you say me what file I can configure. >>> >>> Thank you in advance. >>> >>> Best regards. >>> >>> -- >>> >>> Olivier ROZIER >>> ?quipe nationale de d?veloppement et int?gration >>> d'applications >>> Direction des Syst?mes d'Information >>> DSI >>> >>> Rectorat de Dijon >>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>> >>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>> www.ac-dijon.fr >>> >>> >>> Pensez ? l'environnement avant d'imprimer ce message >>> >>> >>> >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>> >>> >>> >> >> -- >> >> Olivier ROZIER >> ?quipe nationale de d?veloppement et int?gration d'applications >> Direction des Syst?mes d'Information >> DSI >> >> Rectorat de Dijon >> 2G rue du G?n?ral Delaborde - 21000 Dijon >> >> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >> www.ac-dijon.fr >> >> >> Pensez ? l'environnement avant d'imprimer ce message >> >> >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> >> >> > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > > > Pensez ? l'environnement avant d'imprimer ce message > > > > -- Olivier ROZIER ?quipe nationale de d?veloppement et int?gration d'applications Direction des Syst?mes d'Information DSI Rectorat de Dijon 2G rue du G?n?ral Delaborde - 21000 Dijon LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 www.ac-dijon.fr Pensez ? l'environnement avant d'imprimer ce message -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ljnkcnllcmnebalk.png Type: image/png Size: 10841 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0009.png -------------- next part -------------- A non-text attachment was scrubbed... Name: bbgnkdbolnhbflai.png Type: image/png Size: 29662 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0010.png -------------- next part -------------- A non-text attachment was scrubbed... Name: kpohooffghdadohh.png Type: image/png Size: 12767 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0011.png -------------- next part -------------- A non-text attachment was scrubbed... Name: nngllbpincjclfok.png Type: image/png Size: 45549 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0012.png -------------- next part -------------- A non-text attachment was scrubbed... Name: afefophgmgmalphk.png Type: image/png Size: 36953 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0013.png -------------- next part -------------- A non-text attachment was scrubbed... Name: bhklcpmmhlheaefm.png Type: image/png Size: 130924 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0014.png -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0015.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0016.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170905/71f84567/attachment-0017.png From orozier at ac-dijon.fr Thu Sep 7 03:35:57 2017 From: orozier at ac-dijon.fr (Olivier ROZIER) Date: Thu, 7 Sep 2017 09:35:57 +0200 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> <9b2a54c1-3663-e441-c68f-adcde170d548@ac-dijon.fr> Message-ID: <206adcc1-8e86-d8a0-73e9-f1118b4d0602@ac-dijon.fr> Hi Marc, I found the solution! In fact when you run wildfly via the command / / /./bin/standalone.sh -c standalone-apiman.xml / You must add the argument /-b=0.0.0.0 /Therefore, instead of execute the command /./bin/standalone.sh -c standalone-apiman.xml / You must run the command :/ / /./bin/standalone.sh -c standalone-apiman.xml -b=0.0.0.0/ Thank you for your help. Olivier Le 05/09/2017 ? 14:26, Marc Savy a ?crit?: > Hi Olivier, > > Does *hostname* not work for you: > > https://github.com/apiman/apiman/blob/master/distro/vertx/src/main/resources/overlay/configs/conf-es.json#L219 > > You can also alter the reported endpoint with *publicEndpoint*: > > https://github.com/apiman/apiman/blob/master/distro/vertx/src/main/resources/overlay/configs/conf-es.json#L223 > > It seems to work (on 1.3.1.Final, at least), but please verify and let > us know. > > Regards, > Marc > > On 5 September 2017 at 07:32, Olivier ROZIER > wrote: > > Hello Mark, > > I forgot to say you that I use APIMAN 1.3.1.Final overlayfor > Wildfly 10 and APIMAN 1.3.1.Final Vert.x Gateway. > > Thank you for your help. > > Olivier > > > Le 04/09/2017 ? 11:46, Marc Savy a ?crit?: >> Thanks for the clarification, that's helpful. I'll look into it >> and get back to you shortly. >> >> Regards, >> Marc >> >> On 4 September 2017 at 09:47, Olivier ROZIER > > wrote: >> >> Hello Eric, >> >> Thank you for your answer. >> >> In fact, when I say "it doesn't work", I would say that there >> is no result in the client REST but also, there is no error >> message. I haven't got response in fact... >> >> When I execute the command /netstat -ltanu/, I have this result : >> >> As you can see, I have got the line 127.0.0.1:8080 >> but I haven't got the line >> 169.254.107.101:8080 >> >> I think the problem comes from here but I don't know in which >> file I must specify the IP Address and the port >> (169.254.107.101:8080 ). >> >> Moreover, I haven't got firewall. >> >> Do you understand better? >> >> Thank you in advance for your help. >> >> Olivier >> >> >> >> Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit?: >>> When you say it "doesn't work" can you be more specific?? Is >>> the host unreachable or do you receive an error from the >>> Apiman server? >>> >>> I'll assume that the host is simply unreachable and answer >>> that. :) >>> >>> Marc will need to confirm, but I believe the vert.x server >>> automatically binds to 0.0.0.0 when it starts up, so I don't >>> think you should need to configure anything to bind to a >>> specific network host. >>> >>> The only other thing I can think of is that your Ubuntu >>> system has a firewall enabled and that you need to open port >>> 8080 on that firewall so that external TCP requests can be made. >>> >>> https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html >>> >>> >>> -Eric >>> >>> On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER >>> > wrote: >>> >>> Hello, >>> >>> I would like to know how to change the first part of the >>> gateway endpoint. >>> >>> In fact, the endpoint takes this form : >>> >>> http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>> >>> When I try to access to this endpoint from a REST client on local host with this URL : >>> http://localhost:8080/apiman-gateway/ >>> {organizationId}/{API ID}/{API version}/ >>> >>> it works fine. >>> >>> But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : >>> http://172.56.56.123:8080/apiman-gateway/ >>> {organizationId}/{API ID}/{API version}/ >>> >>> it doesn't work. >>> >>> APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). >>> >>> Please, could you say me what file I can configure. >>> >>> Thank you in advance. >>> >>> Best regards. >>> >>> -- >>> >>> Olivier ROZIER >>> ?quipe nationale de d?veloppement et int?gration >>> d'applications >>> Direction des Syst?mes d'Information >>> DSI >>> >>> Rectorat de Dijon >>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>> >>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>> www.ac-dijon.fr >>> >>> >>> Pensez ? l'environnement avant d'imprimer ce message >>> >>> >>> >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>> >>> >>> >> >> -- >> >> Olivier ROZIER >> ?quipe nationale de d?veloppement et int?gration d'applications >> Direction des Syst?mes d'Information >> DSI >> >> Rectorat de Dijon >> 2G rue du G?n?ral Delaborde - 21000 Dijon >> >> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >> www.ac-dijon.fr >> >> >> Pensez ? l'environnement avant d'imprimer ce message >> >> >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> >> >> > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > > > Pensez ? l'environnement avant d'imprimer ce message > > > > -- Olivier ROZIER ?quipe nationale de d?veloppement et int?gration d'applications Direction des Syst?mes d'Information DSI Rectorat de Dijon 2G rue du G?n?ral Delaborde - 21000 Dijon LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 www.ac-dijon.fr Pensez ? l'environnement avant d'imprimer ce message -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170907/d1b11ce1/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170907/d1b11ce1/attachment-0003.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170907/d1b11ce1/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170907/d1b11ce1/attachment-0005.png From marc.savy at redhat.com Thu Sep 7 12:17:32 2017 From: marc.savy at redhat.com (Marc Savy) Date: Thu, 7 Sep 2017 17:17:32 +0100 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: <206adcc1-8e86-d8a0-73e9-f1118b4d0602@ac-dijon.fr> References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> <9b2a54c1-3663-e441-c68f-adcde170d548@ac-dijon.fr> <206adcc1-8e86-d8a0-73e9-f1118b4d0602@ac-dijon.fr> Message-ID: That's for the Servlet version -- perhaps you aren't using Vert.x? On 7 September 2017 at 08:35, Olivier ROZIER wrote: > Hi Marc, > > I found the solution! > > In fact when you run wildfly via the command > > *./bin/standalone.sh -c standalone-apiman.xml * > You must add the argument > > *-b=0.0.0.0 *Therefore, instead of execute the command > > *./bin/standalone.sh -c standalone-apiman.xml * > You must run the command : > > *./bin/standalone.sh -c standalone-apiman.xml -b=0.0.0.0* > > Thank you for your help. > > Olivier > > Le 05/09/2017 ? 14:26, Marc Savy a ?crit : > > Hi Olivier, > > Does *hostname* not work for you: > > https://github.com/apiman/apiman/blob/master/distro/ > vertx/src/main/resources/overlay/configs/conf-es.json#L219 > > You can also alter the reported endpoint with *publicEndpoint*: > > https://github.com/apiman/apiman/blob/master/distro/ > vertx/src/main/resources/overlay/configs/conf-es.json#L223 > > It seems to work (on 1.3.1.Final, at least), but please verify and let us > know. > > Regards, > Marc > > On 5 September 2017 at 07:32, Olivier ROZIER wrote: > >> Hello Mark, >> >> I forgot to say you that I use APIMAN 1.3.1.Final overlayfor Wildfly 10 >> and APIMAN 1.3.1.Final Vert.x Gateway. >> >> Thank you for your help. >> >> Olivier >> >> Le 04/09/2017 ? 11:46, Marc Savy a ?crit : >> >> Thanks for the clarification, that's helpful. I'll look into it and get >> back to you shortly. >> >> Regards, >> Marc >> >> On 4 September 2017 at 09:47, Olivier ROZIER wrote: >> >>> Hello Eric, >>> >>> Thank you for your answer. >>> >>> In fact, when I say "it doesn't work", I would say that there is no >>> result in the client REST but also, there is no error message. I haven't >>> got response in fact... >>> >>> When I execute the command *netstat -ltanu*, I have this result : >>> >>> As you can see, I have got the line 127.0.0.1:8080 but I haven't got >>> the line 169.254.107.101:8080 >>> >>> I think the problem comes from here but I don't know in which file I >>> must specify the IP Address and the port (169.254.107.101:8080). >>> >>> Moreover, I haven't got firewall. >>> >>> Do you understand better? >>> >>> Thank you in advance for your help. >>> >>> Olivier >>> >>> >>> >>> Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit : >>> >>> When you say it "doesn't work" can you be more specific? Is the host >>> unreachable or do you receive an error from the Apiman server? >>> >>> I'll assume that the host is simply unreachable and answer that. :) >>> >>> Marc will need to confirm, but I believe the vert.x server automatically >>> binds to 0.0.0.0 when it starts up, so I don't think you should need to >>> configure anything to bind to a specific network host. >>> >>> The only other thing I can think of is that your Ubuntu system has a >>> firewall enabled and that you need to open port 8080 on that firewall so >>> that external TCP requests can be made. >>> >>> https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html >>> >>> -Eric >>> >>> On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER >>> wrote: >>> >>>> Hello, >>>> >>>> I would like to know how to change the first part of the gateway >>>> endpoint. >>>> >>>> In fact, the endpoint takes this form : >>>> >>>> http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>>> >>>> When I try to access to this endpoint from a REST client on local host with this URL : http://localhost:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>>> >>>> it works fine. >>>> >>>> But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : http://172.56.56.123:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>>> >>>> it doesn't work. >>>> >>>> APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). >>>> >>>> Please, could you say me what file I can configure. >>>> >>>> Thank you in advance. >>>> >>>> Best regards. >>>> >>>> -- >>>> >>>> Olivier ROZIER >>>> ?quipe nationale de d?veloppement et int?gration d'applications >>>> Direction des Syst?mes d'Information >>>> DSI >>>> >>>> Rectorat de Dijon >>>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>>> >>>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>>> www.ac-dijon.fr >>>> Pensez ? l'environnement avant d'imprimer ce message >>>> >>>> >>>> _______________________________________________ >>>> Apiman-user mailing list >>>> Apiman-user at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>> >>>> >>> >>> -- >>> >>> Olivier ROZIER >>> ?quipe nationale de d?veloppement et int?gration d'applications >>> Direction des Syst?mes d'Information >>> DSI >>> >>> Rectorat de Dijon >>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>> >>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>> www.ac-dijon.fr >>> Pensez ? l'environnement avant d'imprimer ce message >>> >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>> >>> >> >> -- >> >> Olivier ROZIER >> ?quipe nationale de d?veloppement et int?gration d'applications >> Direction des Syst?mes d'Information >> DSI >> >> Rectorat de Dijon >> 2G rue du G?n?ral Delaborde - 21000 Dijon >> >> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >> www.ac-dijon.fr >> Pensez ? l'environnement avant d'imprimer ce message >> >> > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > Pensez ? l'environnement avant d'imprimer ce message > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170907/8a48b6b3/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170907/8a48b6b3/attachment-0003.png -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170907/8a48b6b3/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170907/8a48b6b3/attachment-0005.png From orozier at ac-dijon.fr Fri Sep 8 02:36:08 2017 From: orozier at ac-dijon.fr (Olivier ROZIER) Date: Fri, 8 Sep 2017 08:36:08 +0200 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> <9b2a54c1-3663-e441-c68f-adcde170d548@ac-dijon.fr> <206adcc1-8e86-d8a0-73e9-f1118b4d0602@ac-dijon.fr> Message-ID: <73eb1191-c360-23b3-dc5c-e81dce62b5f3@ac-dijon.fr> Hi Marc, I have used this procedure to install APIMAN, wildfly and vert.x : // Step 1 mkdir ~/apiman-1.3.1.Final cd ~/apiman-1.3.1.Final curl http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip -o wildfly-10.1.0.Final.zip curl http://downloads.jboss.org/apiman/1.3.1.Final/apiman-distro-wildfly10-1.3.1.Final-overlay.zip -o apiman-distro-wildfly10-1.3.1.Final-overlay.zip unzip wildfly-10.1.0.Final.zip unzip -o apiman-distro-wildfly10-1.3.1.Final-overlay.zip -d wildfly-10.1.0.Final cd wildfly-10.1.0.Final ./bin/standalone.sh -c standalone-apiman.xml // Step 2 cd ~/apiman-1.3.1.Final curl http://downloads.jboss.org/apiman/1.3.1.Final/apiman-distro-vertx-1.3.1.Final.zip -o apiman-distro-vertx-1.3.1.Final.zip cd apiman-distro-vertx-1.3.1.Final ./apiman-gateway.sh --conf=configs/conf-es.json // Step 3 Add the gateway to the Manager. After that, I write this in the form when I created my API : For your point of view, is it correct? Thank you for your reply. Olivier Le 07/09/2017 ? 18:17, Marc Savy a ?crit?: > That's for the Servlet version -- perhaps you aren't using Vert.x? > > On 7 September 2017 at 08:35, Olivier ROZIER > wrote: > > Hi Marc, > > I found the solution! > > In fact when you run wildfly via the command / > / > > /./bin/standalone.sh -c standalone-apiman.xml / > > You must add the argument /-b=0.0.0.0 > > /Therefore, instead of execute the command > /./bin/standalone.sh -c standalone-apiman.xml > / > You must run the command :/ > / > /./bin/standalone.sh -c standalone-apiman.xml -b=0.0.0.0/ > > Thank you for your help. > > Olivier > > Le 05/09/2017 ? 14:26, Marc Savy a ?crit?: >> Hi Olivier, >> >> Does *hostname* not work for you: >> >> https://github.com/apiman/apiman/blob/master/distro/vertx/src/main/resources/overlay/configs/conf-es.json#L219 >> >> >> You can also alter the reported endpoint with *publicEndpoint*: >> >> https://github.com/apiman/apiman/blob/master/distro/vertx/src/main/resources/overlay/configs/conf-es.json#L223 >> >> >> It seems to work (on 1.3.1.Final, at least), but please verify >> and let us know. >> >> Regards, >> Marc >> >> On 5 September 2017 at 07:32, Olivier ROZIER > > wrote: >> >> Hello Mark, >> >> I forgot to say you that I use APIMAN 1.3.1.Final overlayfor >> Wildfly 10 and APIMAN 1.3.1.Final Vert.x Gateway. >> >> Thank you for your help. >> >> Olivier >> >> >> Le 04/09/2017 ? 11:46, Marc Savy a ?crit?: >>> Thanks for the clarification, that's helpful. I'll look into >>> it and get back to you shortly. >>> >>> Regards, >>> Marc >>> >>> On 4 September 2017 at 09:47, Olivier ROZIER >>> > wrote: >>> >>> Hello Eric, >>> >>> Thank you for your answer. >>> >>> In fact, when I say "it doesn't work", I would say that >>> there is no result in the client REST but also, there is >>> no error message. I haven't got response in fact... >>> >>> When I execute the command /netstat -ltanu/, I have this >>> result : >>> >>> As you can see, I have got the line 127.0.0.1:8080 >>> but I haven't got the line >>> 169.254.107.101:8080 >>> >>> I think the problem comes from here but I don't know in >>> which file I must specify the IP Address and the port >>> (169.254.107.101:8080 ). >>> >>> Moreover, I haven't got firewall. >>> >>> Do you understand better? >>> >>> Thank you in advance for your help. >>> >>> Olivier >>> >>> >>> >>> Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit?: >>>> When you say it "doesn't work" can you be more >>>> specific?? Is the host unreachable or do you receive an >>>> error from the Apiman server? >>>> >>>> I'll assume that the host is simply unreachable and >>>> answer that. :) >>>> >>>> Marc will need to confirm, but I believe the vert.x >>>> server automatically binds to 0.0.0.0 when it starts >>>> up, so I don't think you should need to configure >>>> anything to bind to a specific network host. >>>> >>>> The only other thing I can think of is that your Ubuntu >>>> system has a firewall enabled and that you need to open >>>> port 8080 on that firewall so that external TCP >>>> requests can be made. >>>> >>>> https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html >>>> >>>> >>>> -Eric >>>> >>>> On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER >>>> > wrote: >>>> >>>> Hello, >>>> >>>> I would like to know how to change the first part >>>> of the gateway endpoint. >>>> >>>> In fact, the endpoint takes this form : >>>> >>>> http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>>> >>>> When I try to access to this endpoint from a REST client on local host with this URL : >>>> http://localhost:8080/apiman-gateway/ >>>> {organizationId}/{API ID}/{API version}/ >>>> >>>> it works fine. >>>> >>>> But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : >>>> http://172.56.56.123:8080/apiman-gateway/ >>>> {organizationId}/{API ID}/{API version}/ >>>> >>>> it doesn't work. >>>> >>>> APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). >>>> >>>> Please, could you say me what file I can configure. >>>> >>>> Thank you in advance. >>>> >>>> Best regards. >>>> >>>> -- >>>> >>>> Olivier ROZIER >>>> ?quipe nationale de d?veloppement et int?gration >>>> d'applications >>>> Direction des Syst?mes d'Information >>>> DSI >>>> >>>> Rectorat de Dijon >>>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>>> >>>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>>> www.ac-dijon.fr >>>> >>>> >>>> Pensez ? l'environnement avant d'imprimer ce message >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Apiman-user mailing list >>>> Apiman-user at lists.jboss.org >>>> >>>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>> >>>> >>>> >>> >>> -- >>> >>> Olivier ROZIER >>> ?quipe nationale de d?veloppement et int?gration >>> d'applications >>> Direction des Syst?mes d'Information >>> DSI >>> >>> Rectorat de Dijon >>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>> >>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>> www.ac-dijon.fr >>> >>> >>> Pensez ? l'environnement avant d'imprimer ce message >>> >>> >>> >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>> >>> >>> >> >> -- >> >> Olivier ROZIER >> ?quipe nationale de d?veloppement et int?gration d'applications >> Direction des Syst?mes d'Information >> DSI >> >> Rectorat de Dijon >> 2G rue du G?n?ral Delaborde - 21000 Dijon >> >> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >> www.ac-dijon.fr >> >> >> Pensez ? l'environnement avant d'imprimer ce message >> >> >> >> > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > > > Pensez ? l'environnement avant d'imprimer ce message > > > > -- Olivier ROZIER ?quipe nationale de d?veloppement et int?gration d'applications Direction des Syst?mes d'Information DSI Rectorat de Dijon 2G rue du G?n?ral Delaborde - 21000 Dijon LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 www.ac-dijon.fr Pensez ? l'environnement avant d'imprimer ce message -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170908/7d236b90/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: mhodopnjhidjjnoa.png Type: image/png Size: 43693 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170908/7d236b90/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170908/7d236b90/attachment-0005.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170908/7d236b90/attachment-0006.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170908/7d236b90/attachment-0007.png From julien.gerboud at euranova.eu Fri Sep 8 05:08:33 2017 From: julien.gerboud at euranova.eu (Julien Gerboud) Date: Fri, 08 Sep 2017 09:08:33 +0000 Subject: [Apiman-user] Health Check URL for API Gateway In-Reply-To: References: Message-ID: Marc, I was actually using the wrong URI ( /apiman-gateway*/system/status/ *instead of /apiman-gateway-a*pi/system/status*) and I was not using a basic http auth... With the information you provided me, I was able to configure my load balancer correctly. So thanks a lot!! Regards, On Mon, 4 Sep 2017 at 11:37 Marc Savy wrote: > Julien, > > The standard status endpoint or the *gateway* is: > > http://apimanager:apiman123 > !@localhost:8080/apiman-gateway-api/system/status > > Notice the embedded default username and password (remember to > substitute for whatever security mechanism you set it up) > > I just checked out the 1.3.0.Final image and it seems to work okay for me. > > You can also do the same for the apiman manager endpoint, but instead it > is: > > http://localhost:8080/apiman/system/status > > Let me know if it works for you. > > Regards, > Marc > > On 4 September 2017 at 08:48, Julien Gerboud > wrote: > > Hi Marc, > > > > Thanks for your quick reaction. > > > > I am using the Servlet version. To be more precise, I am using the > Wildfly10 > > docker image with tag 1.3.0.Final (I kept only the gateway part, the > > manager, elasticsearch, keycloak and database are on different > containers). > > > > Regards, > > > > On Sun, 3 Sep 2017 at 19:30 Marc Savy wrote: > >> > >> Hi, > >> > >> Which version of the gateway are you using? Vert.x or Servlet? > >> > >> Regards, > >> Marc > >> > >> > >> On Sunday, September 3, 2017, Julien Gerboud < > julien.gerboud at euranova.eu> > >> wrote: > >>> > >>> Hello to you all, > >>> > >>> I am setting up a load balancer (HA Proxy) in front of 2 (or more) > APIMan > >>> API Gateways. In order to know which instance is up, the load balancer > needs > >>> an health check. > >>> > >>> I tried to use the /system/status/ endpoint of the gateway but I get a > >>> 500 error with a "X-Gateway-Error: Invalid endpoint provided: > >>> /system/status/" header. > >>> > >>> Is there another health check endpoint or a REST Doc for the API > Gateway? > >>> > >>> I am using APIMan version 1.3.0.Final. > >>> > >>> Thanks for your help! > >>> > >>> Regards, > >>> Julien GERBOUD > >>> -- > >>> > >>> ______________________________ > >>> > >>> Julien GERBOUD > >>> > >>> Developer > >>> (M) +32 475 78 05 31 <+32%20475%2078%2005%2031> > >>> > >>> EURA NOVA > >>> > >>> Rue Emile Francqui, 4 > >>> > >>> 1435 Mont-Saint-Guibert > >>> > >>> (T) +32 10 75 02 00 <+32%2010%2075%2002%2000> > >>> > >>> euranova.eu > >>> > >>> research.euranova.eu > >>> > >>> > >>> ? Be green, keep it on the screen > >> > >> > >> > >> -- > >> Sent from mobile phone, apologies for brevity. > > > > -- > > > > ______________________________ > > > > Julien GERBOUD > > > > Developer > > (M) +32 475 78 05 31 <+32%20475%2078%2005%2031> > > > > EURA NOVA > > > > Rue Emile Francqui, 4 > > > > 1435 Mont-Saint-Guibert > > > > (T) +32 10 75 02 00 <+32%2010%2075%2002%2000> > > > > euranova.eu > > > > research.euranova.eu > > > > > > ? Be green, keep it on the screen > -- ______________________________ *Julien GERBOUD* Developer (M) +32 475 78 05 31 <+32%20475%2078%2005%2031> *EURA NOVA* Rue Emile Francqui, 4 1435 Mont-Saint-Guibert (T) +32 10 75 02 00 <+32%2010%2075%2002%2000> *euranova.eu * *research.euranova.eu* -- ? Be green, keep it on the screen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170908/0d88f0ee/attachment.html From marc.savy at redhat.com Thu Sep 21 08:51:23 2017 From: marc.savy at redhat.com (Marc Savy) Date: Thu, 21 Sep 2017 13:51:23 +0100 Subject: [Apiman-user] How to change base url of the gateway endpoint In-Reply-To: <73eb1191-c360-23b3-dc5c-e81dce62b5f3@ac-dijon.fr> References: <403d1fce-ed49-56f1-6f01-ee28ecd36a96@ac-dijon.fr> <0efeeb1a-0aad-1236-28d7-821a9cf36905@ac-dijon.fr> <9b2a54c1-3663-e441-c68f-adcde170d548@ac-dijon.fr> <206adcc1-8e86-d8a0-73e9-f1118b4d0602@ac-dijon.fr> <73eb1191-c360-23b3-dc5c-e81dce62b5f3@ac-dijon.fr> Message-ID: Just verify that you have definitely set your gateway URL correctly and it should work fine (more detail here: https://apiman.gitbooks.io/apiman-installation-guide/installation-guide/quickstart.html#_vert_x_gateway_and_servlet_based_manager ). Regards, Marc On 8 September 2017 at 07:36, Olivier ROZIER wrote: > Hi Marc, > > I have used this procedure to install APIMAN, wildfly and vert.x : > > // Step 1 > mkdir ~/apiman-1.3.1.Final > cd ~/apiman-1.3.1.Final > curl http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip -o wildfly-10.1.0.Final.zip > curl http://downloads.jboss.org/apiman/1.3.1.Final/apiman-distro-wildfly10-1.3.1.Final-overlay.zip -o apiman-distro-wildfly10-1.3.1.Final-overlay.zip > unzip wildfly-10.1.0.Final.zip > unzip -o apiman-distro-wildfly10-1.3.1.Final-overlay.zip -d wildfly-10.1.0.Final > cd wildfly-10.1.0.Final > ./bin/standalone.sh -c standalone-apiman.xml > > // Step 2 > cd ~/apiman-1.3.1.Final > curl http://downloads.jboss.org/apiman/1.3.1.Final/apiman-distro-vertx-1.3.1.Final.zip -o apiman-distro-vertx-1.3.1.Final.zip > cd apiman-distro-vertx-1.3.1.Final > ./apiman-gateway.sh --conf=configs/conf-es.json > > // Step 3 > Add the gateway to the Manager. > > After that, I write this in the form when I created my API : > > > For your point of view, is it correct? > > Thank you for your reply. > > Olivier > > > > Le 07/09/2017 ? 18:17, Marc Savy a ?crit : > > That's for the Servlet version -- perhaps you aren't using Vert.x? > > On 7 September 2017 at 08:35, Olivier ROZIER wrote: > >> Hi Marc, >> >> I found the solution! >> >> In fact when you run wildfly via the command >> >> *./bin/standalone.sh -c standalone-apiman.xml * >> You must add the argument >> >> *-b=0.0.0.0 *Therefore, instead of execute the command >> >> *./bin/standalone.sh -c standalone-apiman.xml * >> You must run the command : >> >> *./bin/standalone.sh -c standalone-apiman.xml -b=0.0.0.0* >> >> Thank you for your help. >> >> Olivier >> >> Le 05/09/2017 ? 14:26, Marc Savy a ?crit : >> >> Hi Olivier, >> >> Does *hostname* not work for you: >> >> https://github.com/apiman/apiman/blob/master/distro/vertx/ >> src/main/resources/overlay/configs/conf-es.json#L219 >> >> You can also alter the reported endpoint with *publicEndpoint*: >> >> https://github.com/apiman/apiman/blob/master/distro/vertx/ >> src/main/resources/overlay/configs/conf-es.json#L223 >> >> It seems to work (on 1.3.1.Final, at least), but please verify and let us >> know. >> >> Regards, >> Marc >> >> On 5 September 2017 at 07:32, Olivier ROZIER wrote: >> >>> Hello Mark, >>> >>> I forgot to say you that I use APIMAN 1.3.1.Final overlayfor Wildfly 10 >>> and APIMAN 1.3.1.Final Vert.x Gateway. >>> >>> Thank you for your help. >>> >>> Olivier >>> >>> Le 04/09/2017 ? 11:46, Marc Savy a ?crit : >>> >>> Thanks for the clarification, that's helpful. I'll look into it and get >>> back to you shortly. >>> >>> Regards, >>> Marc >>> >>> On 4 September 2017 at 09:47, Olivier ROZIER >>> wrote: >>> >>>> Hello Eric, >>>> >>>> Thank you for your answer. >>>> >>>> In fact, when I say "it doesn't work", I would say that there is no >>>> result in the client REST but also, there is no error message. I haven't >>>> got response in fact... >>>> >>>> When I execute the command *netstat -ltanu*, I have this result : >>>> >>>> As you can see, I have got the line 127.0.0.1:8080 but I haven't got >>>> the line 169.254.107.101:8080 >>>> >>>> I think the problem comes from here but I don't know in which file I >>>> must specify the IP Address and the port (169.254.107.101:8080). >>>> >>>> Moreover, I haven't got firewall. >>>> >>>> Do you understand better? >>>> >>>> Thank you in advance for your help. >>>> >>>> Olivier >>>> >>>> >>>> >>>> Le 01/09/2017 ? 17:56, Eric Wittmann a ?crit : >>>> >>>> When you say it "doesn't work" can you be more specific? Is the host >>>> unreachable or do you receive an error from the Apiman server? >>>> >>>> I'll assume that the host is simply unreachable and answer that. :) >>>> >>>> Marc will need to confirm, but I believe the vert.x server >>>> automatically binds to 0.0.0.0 when it starts up, so I don't think you >>>> should need to configure anything to bind to a specific network host. >>>> >>>> The only other thing I can think of is that your Ubuntu system has a >>>> firewall enabled and that you need to open port 8080 on that firewall so >>>> that external TCP requests can be made. >>>> >>>> https://help.ubuntu.com/stable/ubuntu-help/net-firewall-on-off.html >>>> >>>> -Eric >>>> >>>> On Fri, Sep 1, 2017 at 10:39 AM, Olivier ROZIER >>>> wrote: >>>> >>>>> Hello, >>>>> >>>>> I would like to know how to change the first part of the gateway >>>>> endpoint. >>>>> >>>>> In fact, the endpoint takes this form : >>>>> >>>>> http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>>>> >>>>> When I try to access to this endpoint from a REST client on local host with this URL : http://localhost:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>>>> >>>>> it works fine. >>>>> >>>>> But when I try to access to this endpoint from a remote host with the IP address of the host where APIMAN and the gateway are installed like this : http://172.56.56.123:8080/apiman-gateway/{organizationId}/{API ID}/{API version}/ >>>>> >>>>> it doesn't work. >>>>> >>>>> APIMAN and the gateway (vert.x) are installed on the same ubuntu (ssh is activated). >>>>> >>>>> Please, could you say me what file I can configure. >>>>> >>>>> Thank you in advance. >>>>> >>>>> Best regards. >>>>> >>>>> -- >>>>> >>>>> Olivier ROZIER >>>>> ?quipe nationale de d?veloppement et int?gration d'applications >>>>> Direction des Syst?mes d'Information >>>>> DSI >>>>> >>>>> Rectorat de Dijon >>>>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>>>> >>>>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>>>> www.ac-dijon.fr >>>>> Pensez ? l'environnement avant d'imprimer ce message >>>>> >>>>> >>>>> _______________________________________________ >>>>> Apiman-user mailing list >>>>> Apiman-user at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>>> >>>>> >>>> >>>> -- >>>> >>>> Olivier ROZIER >>>> ?quipe nationale de d?veloppement et int?gration d'applications >>>> Direction des Syst?mes d'Information >>>> DSI >>>> >>>> Rectorat de Dijon >>>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>>> >>>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>>> www.ac-dijon.fr >>>> Pensez ? l'environnement avant d'imprimer ce message >>>> >>>> >>>> _______________________________________________ >>>> Apiman-user mailing list >>>> Apiman-user at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>> >>>> >>> >>> -- >>> >>> Olivier ROZIER >>> ?quipe nationale de d?veloppement et int?gration d'applications >>> Direction des Syst?mes d'Information >>> DSI >>> >>> Rectorat de Dijon >>> 2G rue du G?n?ral Delaborde - 21000 Dijon >>> >>> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >>> www.ac-dijon.fr >>> Pensez ? l'environnement avant d'imprimer ce message >>> >>> >> >> -- >> >> Olivier ROZIER >> ?quipe nationale de d?veloppement et int?gration d'applications >> Direction des Syst?mes d'Information >> DSI >> >> Rectorat de Dijon >> 2G rue du G?n?ral Delaborde - 21000 Dijon >> >> LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 >> www.ac-dijon.fr >> Pensez ? l'environnement avant d'imprimer ce message >> >> > > -- > > Olivier ROZIER > ?quipe nationale de d?veloppement et int?gration d'applications > Direction des Syst?mes d'Information > DSI > > Rectorat de Dijon > 2G rue du G?n?ral Delaborde - 21000 Dijon > > > LD : 03 80 44 88 78 - Fax : 03 80 44 88 10 > www.ac-dijon.fr > Pensez ? l'environnement avant d'imprimer ce message > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170921/c9a35d45/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: pfbjfbihimcikhcb.png Type: image/png Size: 207884 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170921/c9a35d45/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: mhodopnjhidjjnoa.png Type: image/png Size: 43693 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170921/c9a35d45/attachment-0005.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 248 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170921/c9a35d45/attachment-0006.png -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7667 bytes Desc: not available Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20170921/c9a35d45/attachment-0007.png From scottpelliott at gmail.com Mon Sep 25 19:10:47 2017 From: scottpelliott at gmail.com (Scott Elliott) Date: Mon, 25 Sep 2017 23:10:47 +0000 Subject: [Apiman-user] CORS issue Message-ID: Why, when the CORS policy plugin is used, do I get multiple Access-Control-Allow-Origin headers in the response. From curl: Origin: http://blah.com Access-Control-Allow-Origin: http://blah.com Access-Control-Allow-Origin: Jetty(9.2.19.v20160908) Chrome does not like the multiple headers, so the API request fails. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170925/6114ee60/attachment.html From marc.savy at redhat.com Tue Sep 26 08:03:46 2017 From: marc.savy at redhat.com (Marc Savy) Date: Tue, 26 Sep 2017 13:03:46 +0100 Subject: [Apiman-user] CORS issue In-Reply-To: References: Message-ID: Hi Scott, Which version of Apiman are you using? Regards, Marc On 26 September 2017 at 00:10, Scott Elliott wrote: > Why, when the CORS policy plugin is used, do I get multiple > Access-Control-Allow-Origin headers in the response. From curl: > > Origin: http://blah.com > > Access-Control-Allow-Origin: http://blah.com > Access-Control-Allow-Origin: Jetty(9.2.19.v20160908) > > Chrome does not like the multiple headers, so the API request fails. > > > > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170926/e732251f/attachment.html From scottpelliott at gmail.com Tue Sep 26 11:56:59 2017 From: scottpelliott at gmail.com (Scott Elliott) Date: Tue, 26 Sep 2017 15:56:59 +0000 Subject: [Apiman-user] CORS issue In-Reply-To: References: Message-ID: 1.2.8.Final On Tue, Sep 26, 2017 at 8:04 AM Marc Savy wrote: > Hi Scott, > > Which version of Apiman are you using? > > Regards, > Marc > > On 26 September 2017 at 00:10, Scott Elliott > wrote: > >> Why, when the CORS policy plugin is used, do I get multiple >> Access-Control-Allow-Origin headers in the response. From curl: >> >> Origin: http://blah.com >> >> Access-Control-Allow-Origin: http://blah.com >> Access-Control-Allow-Origin: Jetty(9.2.19.v20160908) >> >> Chrome does not like the multiple headers, so the API request fails. >> >> >> >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170926/a5e8497a/attachment.html From scottpelliott at gmail.com Tue Sep 26 12:15:58 2017 From: scottpelliott at gmail.com (Scott Elliott) Date: Tue, 26 Sep 2017 16:15:58 +0000 Subject: [Apiman-user] CORS issue In-Reply-To: References: Message-ID: Something wrong with io.apiman.gateway.engine.beans.util.CaseInsensitiveStringMultiMap. The response headers start off with: [Server=Jetty(9.2.19.v20160908), null, null, Date=Tue, 26 Sep 2017 16:08:00 GMT, null, Content-Type=text/html; charset=ISO-8859-1, null, null, null, X-RateMonitor-Limit=1000, null, WWW-Authenticate=Bearer realm="mytest", error="invalid_token", error_description="Token is not active", X-RateMonitor-Remaining=998, null, null, null, X-RateMonitor-Reset=3119, null, null, null, null, null, null, null, null, null, null, null, null, null, null, Cache-Control=must-revalidate,no-cache,no-store] and after the CORS headers are merged, it's: {Access-Control-Allow-Credentials => [true, Bearer realm="mytest", error="invalid_token", error_description="Token is not active"], Access-Control-Allow-Origin => [http://blah.com, Jetty(9.2.19.v20160908)], Cache-Control => [must-revalidate,no-cache,no-store], Content-Type => [text/html; charset=ISO-8859-1], Date => [Tue, 26 Sep 2017 16:08:00 GMT], Server => [Jetty(9.2.19.v20160908)], WWW-Authenticate => [Bearer realm="mytest", error="invalid_token", error_description="Token is not active"], X-RateMonitor-Limit => [1000], X-RateMonitor-Remaining => [998], X-RateMonitor-Reset => [3119]} The "Server" value and the Access-Control-Allow-Origin are somehow merged. On Tue, Sep 26, 2017 at 11:56 AM Scott Elliott wrote: > 1.2.8.Final > > On Tue, Sep 26, 2017 at 8:04 AM Marc Savy wrote: > >> Hi Scott, >> >> Which version of Apiman are you using? >> >> Regards, >> Marc >> >> On 26 September 2017 at 00:10, Scott Elliott >> wrote: >> >>> Why, when the CORS policy plugin is used, do I get multiple >>> Access-Control-Allow-Origin headers in the response. From curl: >>> >>> Origin: http://blah.com >>> >>> Access-Control-Allow-Origin: http://blah.com >>> Access-Control-Allow-Origin: Jetty(9.2.19.v20160908) >>> >>> Chrome does not like the multiple headers, so the API request fails. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>> >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170926/ad7c06aa/attachment.html From marc.savy at redhat.com Tue Sep 26 16:45:41 2017 From: marc.savy at redhat.com (Marc Savy) Date: Tue, 26 Sep 2017 21:45:41 +0100 Subject: [Apiman-user] CORS issue In-Reply-To: References: Message-ID: Hi Scott, This is a symptom of an issue that was fixed in the latest verions of apiman, please upgrade to 1.3.1.Final if possible and let me know if everything seems to be working fine. On 26 September 2017 at 17:15, Scott Elliott wrote: > Something wrong with io.apiman.gateway.engine.beans.util. > CaseInsensitiveStringMultiMap. The response headers start off with: > > [Server=Jetty(9.2.19.v20160908), null, null, Date=Tue, 26 Sep 2017 > 16:08:00 GMT, null, Content-Type=text/html; charset=ISO-8859-1, null, null, > null, X-RateMonitor-Limit=1000, null, WWW-Authenticate=Bearer > realm="mytest", error="invalid_token", error_description="Token is not > active", X-RateMonitor-Remaining=998, null, null, null, > X-RateMonitor-Reset=3119, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, Cache-Control=must-revalidate, > no-cache,no-store] > > and after the CORS headers are merged, it's: > > {Access-Control-Allow-Credentials => [true, Bearer realm="mytest", > error="invalid_token", error_description="Token is not active"], > Access-Control-Allow-Origin => [http://blah.com, > Jetty(9.2.19.v20160908)], Cache-Control => [must-revalidate,no-cache,no-store], > Content-Type => [text/html; charset=ISO-8859-1], Date => [Tue, 26 Sep 2017 > 16:08:00 GMT], Server => [Jetty(9.2.19.v20160908)], WWW-Authenticate => > [Bearer realm="mytest", error="invalid_token", error_description="Token is > not active"], X-RateMonitor-Limit => [1000], X-RateMonitor-Remaining => > [998], X-RateMonitor-Reset => [3119]} > > The "Server" value and the Access-Control-Allow-Origin are somehow merged. > > On Tue, Sep 26, 2017 at 11:56 AM Scott Elliott > wrote: > >> 1.2.8.Final >> >> On Tue, Sep 26, 2017 at 8:04 AM Marc Savy wrote: >> >>> Hi Scott, >>> >>> Which version of Apiman are you using? >>> >>> Regards, >>> Marc >>> >>> On 26 September 2017 at 00:10, Scott Elliott >>> wrote: >>> >>>> Why, when the CORS policy plugin is used, do I get multiple >>>> Access-Control-Allow-Origin headers in the response. From curl: >>>> >>>> Origin: http://blah.com >>>> >>>> Access-Control-Allow-Origin: http://blah.com >>>> Access-Control-Allow-Origin: Jetty(9.2.19.v20160908) >>>> >>>> Chrome does not like the multiple headers, so the API request fails. >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Apiman-user mailing list >>>> Apiman-user at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>> >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170926/2ad493b1/attachment-0001.html From celso.agra at gmail.com Wed Sep 27 00:35:23 2017 From: celso.agra at gmail.com (Celso Agra) Date: Wed, 27 Sep 2017 01:35:23 -0300 Subject: [Apiman-user] How to solve the conflict about CORS and the X-API-Key in header? Message-ID: Hi all, I got some errors with CORS plugin when I try to use my API with a contract. So, I consume my API passing info through header, such as: Authorization, Content-Type, and X-API-Key. I'm talking about a javascript application. So, CORS is a problem for that language. When I configure my contract to allow Cross-Origin, the error still there, but if I put my X-API-Key, as a query parameter, the CORS works fine. Does anyone could help me to understand that? I'm concerned to pass my contract as a query parameter. It should be on Header of my Http Request. Please, help me to understand if it is a behaviour of the application and how can I solve this without use query param. Best Regards, -- --- *Celso Agra* -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170927/7180cce7/attachment.html From scottpelliott at gmail.com Wed Sep 27 11:29:35 2017 From: scottpelliott at gmail.com (Scott Elliott) Date: Wed, 27 Sep 2017 15:29:35 +0000 Subject: [Apiman-user] CORS issue In-Reply-To: References: Message-ID: OK, I tried 1.3.1. Looks like the EAP 7.0 standalone-apiman.xml was not updated to support the Keycloak changes. I used the Wildfly version of the xml file to get it running. However, now it looks like something is wrong with our internal policy plugins that worked in 1.2.8, so I'll have to debug that. Scott On Tue, Sep 26, 2017 at 4:46 PM Marc Savy wrote: > Hi Scott, > > This is a symptom of an issue that was fixed in the latest verions of > apiman, please upgrade to 1.3.1.Final if possible and let me know if > everything seems to be working fine. > > On 26 September 2017 at 17:15, Scott Elliott > wrote: > >> Something wrong >> with io.apiman.gateway.engine.beans.util.CaseInsensitiveStringMultiMap. >> The response headers start off with: >> >> [Server=Jetty(9.2.19.v20160908), null, null, Date=Tue, 26 Sep 2017 >> 16:08:00 GMT, null, Content-Type=text/html; charset=ISO-8859-1, null, null, >> null, X-RateMonitor-Limit=1000, null, WWW-Authenticate=Bearer >> realm="mytest", error="invalid_token", error_description="Token is not >> active", X-RateMonitor-Remaining=998, null, null, null, >> X-RateMonitor-Reset=3119, null, null, null, null, null, null, null, null, >> null, null, null, null, null, null, >> Cache-Control=must-revalidate,no-cache,no-store] >> >> and after the CORS headers are merged, it's: >> >> {Access-Control-Allow-Credentials => [true, Bearer realm="mytest", >> error="invalid_token", error_description="Token is not active"], >> Access-Control-Allow-Origin => [http://blah.com, >> Jetty(9.2.19.v20160908)], Cache-Control => >> [must-revalidate,no-cache,no-store], Content-Type => [text/html; >> charset=ISO-8859-1], Date => [Tue, 26 Sep 2017 16:08:00 GMT], Server => >> [Jetty(9.2.19.v20160908)], WWW-Authenticate => [Bearer realm="mytest", >> error="invalid_token", error_description="Token is not active"], >> X-RateMonitor-Limit => [1000], X-RateMonitor-Remaining => [998], >> X-RateMonitor-Reset => [3119]} >> >> The "Server" value and the Access-Control-Allow-Origin are somehow merged. >> >> On Tue, Sep 26, 2017 at 11:56 AM Scott Elliott >> wrote: >> >>> 1.2.8.Final >>> >>> On Tue, Sep 26, 2017 at 8:04 AM Marc Savy wrote: >>> >>>> Hi Scott, >>>> >>>> Which version of Apiman are you using? >>>> >>>> Regards, >>>> Marc >>>> >>>> On 26 September 2017 at 00:10, Scott Elliott >>>> wrote: >>>> >>>>> Why, when the CORS policy plugin is used, do I get multiple >>>>> Access-Control-Allow-Origin headers in the response. From curl: >>>>> >>>>> Origin: http://blah.com >>>>> >>>>> Access-Control-Allow-Origin: http://blah.com >>>>> Access-Control-Allow-Origin: Jetty(9.2.19.v20160908) >>>>> >>>>> Chrome does not like the multiple headers, so the API request fails. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Apiman-user mailing list >>>>> Apiman-user at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>>> >>>>> >>>> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170927/c145b190/attachment.html From marc.savy at redhat.com Wed Sep 27 12:09:51 2017 From: marc.savy at redhat.com (Marc Savy) Date: Wed, 27 Sep 2017 17:09:51 +0100 Subject: [Apiman-user] CORS issue In-Reply-To: References: Message-ID: Thanks, I'll try to check that out EAP config issue and endeavour to roll it into the next release (which should be done shortly). https://issues.jboss.org/browse/APIMAN-1286 I can't think of any deliberate changes to the policy engine between 1.2.8.Final and 1.3.1.Final, so if you discover something untoward please let me know. On 27 September 2017 at 16:29, Scott Elliott wrote: > OK, I tried 1.3.1. Looks like the EAP 7.0 standalone-apiman.xml was not > updated to support the Keycloak changes. I used the Wildfly version of the > xml file to get it running. However, now it looks like something is wrong > with our internal policy plugins that worked in 1.2.8, so I'll have to > debug that. > > Scott > > On Tue, Sep 26, 2017 at 4:46 PM Marc Savy wrote: > >> Hi Scott, >> >> This is a symptom of an issue that was fixed in the latest verions of >> apiman, please upgrade to 1.3.1.Final if possible and let me know if >> everything seems to be working fine. >> >> On 26 September 2017 at 17:15, Scott Elliott >> wrote: >> >>> Something wrong with io.apiman.gateway.engine. >>> beans.util.CaseInsensitiveStringMultiMap. The response headers start >>> off with: >>> >>> [Server=Jetty(9.2.19.v20160908), null, null, Date=Tue, 26 Sep 2017 >>> 16:08:00 GMT, null, Content-Type=text/html; charset=ISO-8859-1, null, null, >>> null, X-RateMonitor-Limit=1000, null, WWW-Authenticate=Bearer >>> realm="mytest", error="invalid_token", error_description="Token is not >>> active", X-RateMonitor-Remaining=998, null, null, null, >>> X-RateMonitor-Reset=3119, null, null, null, null, null, null, null, null, >>> null, null, null, null, null, null, Cache-Control=must-revalidate, >>> no-cache,no-store] >>> >>> and after the CORS headers are merged, it's: >>> >>> {Access-Control-Allow-Credentials => [true, Bearer realm="mytest", >>> error="invalid_token", error_description="Token is not active"], >>> Access-Control-Allow-Origin => [http://blah.com, >>> Jetty(9.2.19.v20160908)], Cache-Control => [must-revalidate,no-cache,no-store], >>> Content-Type => [text/html; charset=ISO-8859-1], Date => [Tue, 26 Sep 2017 >>> 16:08:00 GMT], Server => [Jetty(9.2.19.v20160908)], WWW-Authenticate => >>> [Bearer realm="mytest", error="invalid_token", error_description="Token is >>> not active"], X-RateMonitor-Limit => [1000], X-RateMonitor-Remaining => >>> [998], X-RateMonitor-Reset => [3119]} >>> >>> The "Server" value and the Access-Control-Allow-Origin are somehow >>> merged. >>> >>> On Tue, Sep 26, 2017 at 11:56 AM Scott Elliott >>> wrote: >>> >>>> 1.2.8.Final >>>> >>>> On Tue, Sep 26, 2017 at 8:04 AM Marc Savy wrote: >>>> >>>>> Hi Scott, >>>>> >>>>> Which version of Apiman are you using? >>>>> >>>>> Regards, >>>>> Marc >>>>> >>>>> On 26 September 2017 at 00:10, Scott Elliott >>>>> wrote: >>>>> >>>>>> Why, when the CORS policy plugin is used, do I get multiple >>>>>> Access-Control-Allow-Origin headers in the response. From curl: >>>>>> >>>>>> Origin: http://blah.com >>>>>> >>>>>> Access-Control-Allow-Origin: http://blah.com >>>>>> Access-Control-Allow-Origin: Jetty(9.2.19.v20160908) >>>>>> >>>>>> Chrome does not like the multiple headers, so the API request fails. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Apiman-user mailing list >>>>>> Apiman-user at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>>>> >>>>>> >>>>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170927/98f24b12/attachment-0001.html