Hello, I had recently(about two weeks ago) gotten some changes merged into the express-gateway repo. My team is super excited to make use of the new functionality that we had helped contribute to and was hoping to get a timeline on when a new version would be published? I had reached out on github and got no response.
Hi everyone. I was curious about the oauth2.0 introspection plugin. In the documentation https://www.express-gateway.io/docs/policies/oauth2-introspection/, it says that you must provide an authorization_value which represents the client_id/secret combo. This makes total sense for all cases outside of PCKE application where a client secret is not given. A major integration player who does this is okta. https://developer.okta.com/docs/reference/api/oidc/#introspect. Given that info, my question is - Is the plugin unable to handle the okta introspection for a pkce app given that an Authorization Header must not be provided.
Hi. I have a couple of questions around basic-auth credentials. I am trying to make a basic-auth credential for a user via the admin api. Can you set the password you want the user to have? Can you update the credential with a new password? I am trying to secure an endpoint via basic-auth which will allow for a creation of a jwt token to access the rest of the gateway. When a new user gets created I want to create a basic-auth credential with the password the user added and allow them to reset the password. I have been looking at the documents ans can't see anything about this, but I thought that it would be a basic requirement of the system. Maybe I am not understanding the credential system usage correctly.
Hi, I'm currently trying to get responses from an AWS lambda which are base64 encoded gzip binary data to be returned to the client as regular JSON. So far I haven't been able to come up with a solution using both express-gateway-plugin-compression and express-gateway-plugin-lambda. What would your recommendation be for this? To be clear the only compression I want to exist is on the response of the lambda to the gateway, everything else is uncompressed. Thanks in advance!
2 replies
I am getting connect EADDRNOTAVAIL 127.0.0.1:9015 - Local (127.0.0.1:0) this error
Hi, everyone! I would like to get all the users... So I use GET https://{my_url}/gateway/admin/users?start=0. It returns the first user and a nextKey value. But when I make a new search using GET https://{my_url}/gateway/admin/users?start={nextKey value of previous search}, there's no more records inside this search. But I still have more users. Could anyone here help me, please?
Hi, can someone take a look at this performance issue: https://stackoverflow.com/questions/63723869/express-gateway-degraded-causing-huge-delays-on-requests I really appreciate any help
hi, has somebody an answer to this: https://stackoverflow.com/questions/59753630/is-there-a-simple-way-to-generate-api-documentation-from-express-gateway-service ?
hi, has somebody an answer to this: https://stackoverflow.com/questions/59753630/is-there-a-simple-way-to-generate-api-documentation-from-express-gateway-service ?
bump!
because golang is multi-threaded
??
followed document https://www.express-gateway.io/docs/policies/oauth2-introspection/
express gateway is not passing header
Hello. So I am looking at the express-gateway document for req/resp data transformation and it is unclear how this api gateway transformation data such as xml to json, json to xml as a gateway should do before sending to a micro-service? I found this article in the blog, but that talks about using express directly. Am I missing or not understanding how express-gateway req/resp transform plug-ins work or does express-gateway just not support that?
Hi Everyone! I am trying to use the CORS policy for one of my endpoints. But no matter what setting I provide, it allows the request to pass through. I want to restrict the endpoint access to a particular origin. Need some help!
This is how I am trying to configure the CORS policy:
This is how I am trying to configure the CORS policy:
apiEndpoints:
- auth
policies:
- cors:
- action:
origin: [http://www.example.com]
methods: "OPTIONS,POST"
optionsSuccessStatus: 204
please help me this problem
hello everyone, I want to know if we can change remote express gateway config from outside. Is there a api exposed for admins, to enable changing config without having to change the docker image of eg?
Our use case is we have an infrastructure based on tenants and want to change the config in run time without having container restarts or image changes
http:
port: 9000
admin:
port: 9876
hostname: localhost
apiEndpoints:
cust:
host: localhost
paths:- '/delete' - '/update'serviceEndpoints:
custsurv:
url: 'http://localhost:3000'
policies:
- basic-auth
- cors
- expression
- key-auth
- log
- oauth2
- proxy
- rate-limit
pipelines:
default:
apiEndpoints:
- cust
policies:- rate-limit:
- action:
Limit to 1 per minute
max: 1
windowMs: 100000- proxy:
- action:
serviceEndpoint: custsurv
changeOrigin: true