I'm talking about a serviceEndpoint in the gateway.config.yml file.
Hi, I have issues with Basic Auth / Redis performances.
I created a stackoverflow post https://stackoverflow.com/questions/58977214/express-gateway-basic-auth-redis-performances-issue
Maybe you can help me figure it out ?
I created a stackoverflow post https://stackoverflow.com/questions/58977214/express-gateway-basic-auth-redis-performances-issue
Maybe you can help me figure it out ?
Do you think auth providers are the best way to manage authentications in eg ?
I'm not a developer of eg and I'm discovering the product. But keyclaok eg plugin is based on nodejs keycloak adapter. I(s a clever solution because thsi adapter is maintained by keyclaok and it proposes full keycloak feature. I have to investigate its behaviour and management of session and cookie in HA mode with redis sentinel. Modiying code, it's possible to protect sub resource with different stategy (realm, client,...)If you are working on it, im' interested for your feedback @glony_gitlab
I cannot get express-gateway to work with OAuth2 AND a GraphQL (POST) endpoint. OAuth2 with a regular GET endpoint works fine, and so does key-auth (or no auth) and the GraphQL POST endpoint. But OAuth2 and GraphQL together doesn't work. Can anyone point me in the right direction please? Something I forgot in my gateway.config.yml maybe?
I couldn't find a way to make logging conditional on NODE_ENV other than to create a custom condition like this.
In the condition file:
handler: (conditionConfig) => () => (
process.env[conditionConfig.variableName] === conditionConfig.expected
)In the gateway config:
- log:
- condition:
name: not
condition:
name: environment-variable-match
variableName: NODE_ENV
expected: testAm I doing this the hard way? If not, should I publish this as a tiny plugin?
how to translate xml to json using express gateway
https://www.npmjs.com/package/xml2json + custom EG plugin = community contribution :) @Wassemoo (https://github.com/ExpressGateway/express-gateway-plugin-example)
How do I have to configure an app like Insomnia or Postman to get an access token? I get it to work on a browser following the instructions on https://www.express-gateway.io/getting-started-with-oauth2/, but Insomnia gives me a "Failed to fetch token url=[url-to-api-gateway]/oauth2/token status=401". What am I doing wrong?
(I'm talking about OAuth2 as means of authorization.)
Has anyone any idea why /oauth2/token is returning a 401 error (I'm using Insomnia)? My client id is the id of the application created with
eg apps create, but what is the client secret? Is /oauth2/token giving me a 401 (no authorization) because I didn't sent a client secret?
Hello, please, I need some help here. I'm trying to run through the OAuth2 flow using cURL. On /oauth2/authorize I get a "Found. Redirecting to /login". Is there a way to send my basic-auth information using cUrl to avoid this redirection? I'm looking for a way to do the whole OAuth2 authentification thing over the command line, or using JavaScript's fetch. Any documentation I can read about this? Thanks…
I'm trying jwt on express-gateway. But from the configuration gateway.config.yml it is in accordance with the documentation. but, thats always return unautorized. my gateway.config.yml:
http:
port: 8080
admin:
port: 9876
host: localhost
apiEndpoints:
authAPI:
host: localhost
paths:
- '/users/signin'
- '/users/signup'
- '/users/oauth/facebook'
- '/users/auth/google'
- '/users/auth/google/callback'
- '/users/secret'
- '/users/get-user-google'
- '/dashboard'
crudAPI:
host: localhost
paths:
- '/users/get-user-data'
- '/users/delete-user-data'
- '/users/add-user-data'
- '/users/get-one-user-data/*'
- '/users/update-user-data'
- '/users/update-pass-user-data'
serviceEndpoints:
authService:
url: 'http://localhost:3003'
crudService:
url: 'http://localhost:3004'
policies:
- log
- oauth2
- proxy
- jwt
pipelines:
crud:
apiEndpoints:
- crudAPI
policies:
- log:
- action:
message: "here"
- jwt:
- action:
secretOrPublicKey: secretAuth
checkCredentialExistence: false
# passThrough: true
- proxy:
- action:
serviceEndpoint: crudService
changeOrigin: true
auth:
apiEndpoints:
- authAPI
policies:
- log:
- action:
message: "here auth"
- proxy:
- action:
serviceEndpoint: authService
if passThrough set to true (or uncomment) its work correctly. something went wrong?
help
Configuring yargs through package.json is deprecated and will be removed in a future major release, please use
the JS API instead.
? Enter firstname [required]: bala
? Enter lastname [required]: subramanyam
? Enter username [required]: bala
? Enter email: balupamujula@gmail.com
? Enter redirectUri: http://localhost:8080/api/v1/
× connect ECONNREFUSED 127.0.0.1:9876
PS E:\incedo-training-project\scalable-microservices\egateway> eg users create? Enter username [required]: bala
? Enter email: balupamujula@gmail.com
? Enter redirectUri: http://localhost:3002/api/v1/
× connect ECONNREFUSED 127.0.0.1:9876
PS E:\incedo-training-project\scalable-microservices\egateway>
the JS API instead.
? Enter firstname [required]: bala
? Enter lastname [required]: subramanyam
? Enter username [required]: bala
? Enter email: balupamujula@gmail.com
? Enter redirectUri: http://localhost:8080/api/v1/
× connect ECONNREFUSED 127.0.0.1:9876
PS E:\incedo-training-project\scalable-microservices\egateway> eg users create? Enter username [required]: bala
? Enter email: balupamujula@gmail.com
? Enter redirectUri: http://localhost:3002/api/v1/
× connect ECONNREFUSED 127.0.0.1:9876
PS E:\incedo-training-project\scalable-microservices\egateway>
zone-evergreen.js:2952 GET http://13.84.42.7:8080/api/v3/Users/26fbd657-9ac6-489c-b2bb-12f4557c3bc 502 (Bad Gateway)
Hola! We are using Express-Gateway in a K8s (Kubernetes) setup. We have noticed as we scale express-gateway pods up there tends to be some 502 errors when express-gateway connects to services (pods) behind it and defined in the apiEndpoints. Has anyone experienced this using K8s with gateway?
@codersbrew the project is not dead (see github https://github.com/ExpressGateway/express-gateway/commits/master) but the community is not active. It's perhaps the weak point of this product :(
