Elasticsearch configuration
by Aikeaguinea
I'm moving toward a production deployment of apiman on AWS. At least for
now we're using Amazon's Elasticsearch service and have been able to
configure and use it.
For production, we need to pay attention to some of the finer details of
clustering, etc. It looks like sharding is mainly controlled when an
index is created. How does apiman manage creating replica shards? Does
this need to be configured somehow?
--
http://www.fastmail.com - IMAP accessible web-mail
8 years, 10 months
Extending the Client lifecycle
by michele danieli
I have to integrate an external (and existing) Authentication provider that
will support the OAuth flow.
While I understand the implementation aspects of the plugin (looking at the
code was useful) I am wondering how can I extend the client life-cycle in
order to create a client on the external provider (via a REST end-point)
and receive a client id and secret. Additionally I would like to extend
the client model in order to make this information in the ClientApp
property page.
Anyone considered a similar scenario?
Thanks
Michele
8 years, 10 months
FWD Re: Error 401 - Unit test with gateway
by Marc Savy
To avoid further duplicated replies, fwding Charles' mail to me...
-------- Forwarded Message --------
Problem solved. My karaf unit test missed the file containing the Jetty
REALM to authenticate the use.
On 19/02/16 20:34, Marc Savy wrote:
> The only thing I can imagine is that you constructed the Authorization
> header incorrectly and/or the test isn't using the auth information
> you're assuming?
>
> It's impossible to guess from the information you've provided I'm afraid
>
> On 19/02/2016 18:17, Charles Moulliard wrote:
>> Hi,
>>
>> I have developed a unit test to control the REST Gateway Api when
>> deployed into Karaf using Apache HttpClient but when I issue this
>> request
>>
>> https://localhost:8444/apiman-gateway-api/system/status
>>
>> I receive an error 401
>>
>> https://gist.githubusercontent.com/cmoulliard/daa13f336b04ba625af4/raw/f9...
>>
>>
>> 2016-02-19 19:09:10,722 | INFO | (3)-192.168.1.80 |
>> HttpServiceFactoryImpl | 66 -
>> org.ops4j.pax.web.pax-web-runtime - 3.2.4 | Unbinding bundle:
>> [io.apiman.apiman-gateway-osgi-api [212]]
>> javax.servlet.ServletException
>> at org.eclipse.jetty.server.Request.login(Request.java:2109)
>> at
>> io.apiman.common.servlet.AuthenticationFilter.doBasicAuth(AuthenticationFilter.java:232)
>>
>>
>> As the same request works pretty well when issued using curl/httpie tool
>> against the Karaf container running in standalone mode, I 'm wondering
>> why it fails with HttpClient & Basic Authentication ?
>>
>> Regards,
>>
>> Charles
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>
>
8 years, 10 months
Error 401 - Unit test with gateway
by Charles Moulliard
Hi,
I have developed a unit test to control the REST Gateway Api when
deployed into Karaf using Apache HttpClient but when I issue this request
https://localhost:8444/apiman-gateway-api/system/status
I receive an error 401
https://gist.githubusercontent.com/cmoulliard/daa13f336b04ba625af4/raw/f9...
2016-02-19 19:09:10,722 | INFO | (3)-192.168.1.80 |
HttpServiceFactoryImpl | 66 -
org.ops4j.pax.web.pax-web-runtime - 3.2.4 | Unbinding bundle:
[io.apiman.apiman-gateway-osgi-api [212]]
javax.servlet.ServletException
at org.eclipse.jetty.server.Request.login(Request.java:2109)
at
io.apiman.common.servlet.AuthenticationFilter.doBasicAuth(AuthenticationFilter.java:232)
As the same request works pretty well when issued using curl/httpie tool
against the Karaf container running in standalone mode, I 'm wondering
why it fails with HttpClient & Basic Authentication ?
Regards,
Charles
8 years, 10 months
Test util class to start ES
by Charles Moulliard
Hi,
Do we have a utility class that we can use to create an instance of
Elasticsearch that we can start before to run a unit test ?
Regards,
Charles
8 years, 10 months
Change default gateway instance
by Charles Moulliard
Hi,
Is it possible to change during installation (download of apiman distro,
wildfly9, unzip, ...) of Apiman Manager the gateway defined by default
(Gateway name: 'The Gateway , description: 'This is the gateway',
Configuration endpoint: 'https://localhost:8443/apiman-gateway-api') . I
would like to delete the existing and add a new one corresponding to an
external Apiman Gateway ?
Regards,
Charles
8 years, 11 months
Deploy Apiman Manager, Gateway, Elasticsearch locally - new bash script
by Charles Moulliard
Hi,
FYI, I have created a new bash script to install / deploy locally Apiman
on one machine. Here is the link of the PR :
https://github.com/apiman/apiman-deployer/pull/1
When you will use it, you can accept the default values
Apiman Version :1.2.1.Final
ElasticSearch Version :1.7.2
Wildfly version : 9.0.2.Final
ElasticSearch Server : http://localhost:9200
Apiman Manager : http://localhost:8080. (Keycloak Server is running with
Apiman Manager)
Database : h2
Apiman Gateway :
Gateway Public Endpoint : https://localhost:8543/apiman-gateway/
Keycloak Server : https://localhost:8443/auth
Here is the offset of the port defined
- Apiman Manager offset: 0 (-> 8080, 8443)
- Apiman Gateway offset: 100 (-> 8180, 8543)
- Apiman Keycloak Server offset: 200 (-> 8280, 8643)
Remark :
- The script has been tested on MacOS X (= Darwin OS) with the
simple-echo service part of the apiman-quickstart project (mvn jetty:run).
http --verify=no GET https://localhost:8543/apiman-gateway/fuse/echo/1.0
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 317
Content-Type: application/json
Date: Tue, 02 Feb 2016 11:58:29 GMT
Server: Jetty(9.3.0.v20150612)
X-Powered-By: Undertow/1
{
"bodyLength": null,
"bodySha1": null,
"headers": {
"Accept": "*/*",
"Accept-Encoding": "gzip, deflate",
"Connection": "keep-alive",
"Host": "localhost:9999",
"User-Agent": "HTTPie/0.9.2"
},
"method": "GET",
"resource": "/apiman-echo/hello",
"uri": "/apiman-echo/hello"
}
- The only thing that I have done manually is to add a NEW gateway
within the Apiman Manager GUI
(http://localhost:8080/apimanui/api-manager/admin/gateways) using this
address : https://localhost:8543/apiman-gateway/ and user : apimanager &
pwd : apiman123!
Regards,
--
Charles Moulliard
Principal Solution Architect / JBoss Fuse Expert - Global Enablement @redhat
cmoulliard(a)redhat.com | work: +31 205 65 12 84 | mobile: +32 473 604 014
MC-Square Business "Stockholm", Leonardo Da Vincilaan 19, Diegem 1831 -
Belgium
twitter: @cmoulliard <http://twitter.com/cmoulliard> | blog:
cmoulliard.github.io <http://cmoulliard.github.io>
committer: apache camel, karaf, servicemix, hawtio, fabric8, drools,
jbpm, deltaspike
8 years, 11 months
