How do I configure interaction between my own authentication server and Express-Gateway? can someone help please?
I want to build simple gateway with express-gateway
My config is like below
port: 8080
admin:
port: 9876
apiEndpoints:
api:
host: localhost
paths: "/ip"
hr:
methods: 'GET,POST,PUT'
host: localhost
paths: '/api*'
serviceEndpoints:
httpbin: # will be referenced in proxy policy
url: 'https://httpbin.org'
hrService: # will be referenced in proxy policy
url: 'http://localhost:5000'
policies:
- basic-auth
- cors
- expression
- key-auth
- log
- oauth2
- proxy
- rate-limit
pipelines:
default:
apiEndpoints:
- api
policies:
- proxy:
- action:
serviceEndPoint: httpbin
changeOrigin: true
hr:
apiEndpoints:
- hr
policies:
-
cors:
- action:
origin: '*'
methods: ['HEAD','PUT','PATCH','POST','DELETE']
-
proxy:
- action:
serviceEndPoint: hrService
Looks like I copied and pasted the sample config but I am getting Bad Gateway response in postman
hrService endpoint is working correctly
but can't reach via gateway
And
httpbin endpoint does also respond with bad gateway
what's wrong in my config?
This is postman response
Hi everyone
I've got a problem that I want to add some extra request header when the request pass though the express-gateway.
But I failed with the request-transformer plugin.
Also the
Here's my config.yaml file:
I've got a problem that I want to add some extra request header when the request pass though the express-gateway.
But I failed with the request-transformer plugin.
Also the
headers in pipeline optional reference not works.Here's my config.yaml file:
pipelines:
aggregate:
apiEndpoints:
- aggregateAPIs
policies:
- log: # policy name
- action: # array of condition/actions objects
message: ${req.method} ${req.originalUrl} # parameter for log action
- cors:
- action:
origin: 'http://localhost:4200'
methods: 'PUT,POST,GET,DELETE,OPTIONS'
allowedHeaders: ['X-Requested-With', 'Authorization', 'content-type']
credentials: true
- sso:
- key-auth:
- condition:
name: expression
expression: "req.headers['authorization']? req.headers['authorization'].indexOf('apiKey') == 0 : false"
action:
message: "consumer key"
- onboard:
- condition:
name: expression
expression: "req.headers['eg-consumer-id']"
action:
message: "3rd party user onboard process"
- acl:
- expression:
- action:
jscode: 'req.url.indexOf("/cogarch/api") == 0 ? req.url = req.url.substring(8, req.url.length) : null;'
- error:
- proxy: # policy name
- action:
serviceEndpoint: aggregateService
changeOrigin: true
headers:
request-header-test: "request-header-test"
1 reply
Hi :wave: Team, I've created two react apps -- one serving on port 3000 and the other serving on port 4000 on my local machine and set up express gateway in front of them. Although I can see the proper
sources being shown in the browser's developer tools when I hit the gateway endpoint, the browser is not rendering those pages. The pages are rendering correctly when I hit the individual endpoints corresponding to the react apps. Any idea where I'm going wrong?
Not sure if this is relevant, but the each of the two apps have multiple routes operating within them (Using react's
BrowserRouter)
When I follow the credential creation instructions on https://www.express-gateway.io/getting-started/, I get hung up indefinitely after I run the
eg credentials create command.
I get three messages after I execute the command. All three say "Configuring yargs through package.json is deprecated and will be removed in a future major release, please use the JS API instead."
The credentials appear to be created;
eg credentials list shows all the attempts I made. But when I retry my cURL against the http://localhost:8080/ip I get a string of HTML that ultimate spells out "Cannot GET /ip"
However, that only solves the problem with the 'Cannot GET /ip". It does not solve the indefinite hang up after executing
eg credentials create
How To Use Environment Variables In Express Gateway ?run different env with gateway.config.yaml，i can not watch video with https://vimeo.com/259108554
To allow only certain endpoints?
like i should be able to map API's against API key. if user hits any other endpoint it should give error in response
example /hello /world /hi are 3 apis. /hello and /world is mapped to app1. if he tries to access /hi he should get unauthorized or invalid access error
As he is only authorized to use /hello and /world api only
@samuelkitazume:matrix.org Can you comment ?
If you cannot do that through the built in authorization... you can use a custom plugin for that
Hmm I meant you can code your custom plugin. In the project I was working on early this year I had to rely on AD groups, so I came up with a bunch of plugins...
Its very easy and straightforward
I'm trying to implement
helmet (https://www.npmjs.com/package/helmet) as a custom policy within express-gateway, but I don't have access to the gatewayExpressApp to apply this globally at the gateway level, is there another way to implement this?
Hello. Can someone explain what I'm doing wrong please? I'm forwarding to a service, but it appears to be adding a trailing slash. If I hit localhost:9999/api/v1/apiary, it forwards to apiary:3000/crud/ (with the trailing slash) even though I've configured without the trailing slash (see gist for config - https://gist.github.com/MrSimonEmms/461ec255a73d55c09b4d6e945be0df5d)
If I remove the /crud on the service, it doesn't put a trailing slash on
if the response is: [{"test":"test","test2":"test2"},{"test":"test","test2":"test2"}] I would like to remove test property
