Repository navigation
Replies: 2 comments 2 replies
|
Hi @FoxxMD, I took a break from working on this project while starting a new job. Will make this work for your use cases and get started on bi-weekly releases. Give me 2-3 days to complete the work and test. Thank you. |
1 reply
|
@FoxxMD sorry for such a delay. I released the requested features. See the release notes.. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi, I'm back again giving doorman another try.
I'm having a hard time determining if my scenario is viable just from poking around in the application. Can you please let me know if it's possible to replicate this?
I'm currently using Apache APISIX as a gateway for some selfhosted services. My requirements, which apisix satisifies, are:
Provide Transparent URL Access to Upstream Services
I have an upstream service at
https://foo.mydomain.comthat would normally serve api calls at endpoints likehttps://foo.mydomain.com/v2/bar/query?paramA=valuehttps://foo.mydomain.com/v2/taz/query?paramC=valueI can point my reverse proxy at APISIX for all
foo.mydomain.comroutes and APISIX can route to the upstream service based on the fact the request is for hostfoo.mydomain.com, even though APISIX doesn't "live" at this domain itself (for UI/administration).So, to my end users,
foo.mydomain.comis the actual service they expect it to be. The API gateway is wire-compatible with client libraries that would normally communicate with the real service atfoo.mydomain.comIE if I was to point my reverse proxy directly at the upstream service there would be no disruption to my end users.Anonymous Access
APISIX allows treating requests that are not authorized (IE missing
Authorizationheader, or something) as an Anonymous user/group/role. Which can be assigned credits/rate limiting/etc. properties the same as any other user/role/group.This allows me to offer a "basic" tier of access to anonymous users so there is "public" access possible for a gateway-d service.
Rate Limiting (Credits) By IP
To work with the above anonymous access, rate limiting can be done by IP and/or per user/role/group. So that all Anonymous users are not aggregated into one bucket for credits. But I can still assign rate limiting per api key for authorized users.
Is it possible to do these things with doorman? Thanks for taking the time to read/respond.
All reactions