-
Notifications
You must be signed in to change notification settings - Fork 351
Issues: ExpressGateway/express-gateway
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Feature: programmatic startup/shutdown improvements
enhancement
#422
opened Sep 21, 2017 by
XVincentX
Return the proper status codes from the WebAPI
good first contribution
good first issue
#593
opened Jan 2, 2018 by
XVincentX
User scopes do not get propagated to the returned JWT provided by EG
bug
next-sprint
#740
opened May 28, 2018 by
XVincentX
How to bind express-gateway "host" to localhost and use an Nginx reverse proxy?
#1004
opened Aug 6, 2020 by
Nditah
credentials: app users should have credential type with 2 keys - app + user
bug
#626
opened Feb 1, 2018 by
altsang
Empty string shouldn't be allowed as basic-auth/oauth2 custom password
bug
#774
opened Aug 1, 2018 by
kolbinski
Model schemas are strictly required even when auth policies are not used.
bug
#760
opened Jun 22, 2018 by
kevinswiber
Can we use same redis instance for multiple Express-Gateways instance on different server?
#1030
opened Jul 6, 2021 by
pprathameshmore
1 of 2 tasks
EG should differentiate the error between unauthorized and invalid token
#701
opened Apr 18, 2018 by
djesani
Previous Next
ProTip!
Updated in the last three days: updated:>2025-01-25.