-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
CORS + API Auth breaks #863
Comments
There are some issues with auth #848 You will hear back from us soon. |
@ironhacker able to replicate with a simple vue app |
The pre-flight request is getting blocked by Auth filter. |
Hi, |
Solution outline
|
This bug has been fixed in the latest release, can we close this issue now? |
Yes go ahead
…On Sun, Mar 9, 2025, 5:50 AM Ameya Kulkarni ***@***.***> wrote:
This bug has been fixed in the latest release, can we close this issue now?
—
Reply to this email directly, view it on GitHub
<#863 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAISPRDWYLY2EL2ULE3I7BL2TQMF7AVCNFSM6AAAAABYBOFGJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYG44TGOJRGI>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
[image: AmeyaKulkarni2001]*AmeyaKulkarni2001* left a comment
(9tigerio/db2rest#863)
<#863 (comment)>
This bug has been fixed in the latest release, can we close this issue now?
—
Reply to this email directly, view it on GitHub
<#863 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAISPRDWYLY2EL2ULE3I7BL2TQMF7AVCNFSM6AAAAABYBOFGJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYG44TGOJRGI>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
It seems that I do not have permission to close a issue, probably cause I have not created it @ironhacker or @kdhrubo could you close this issue? Also should the documentation also be updated for the new parameter introduced and for how the CORS is now used? |
Yes doc has to be updated thats pending. @ironhacker can you pls check the latest release and confirm this is resolved for you. |
I downloaded and compiled main to get the new CORS support and it works OK until I enable API Auth. Either setting works on its own, but both combined fail with a 401 Unauthorized on the preflight request. If I make the same GET request from Postman (no preflight) with API Key it's good.
CORS + ENABLE_AUTH=false (this works fine)
CORS + ENABLE_AUTH=true (works in Postman, but fails in Browser with 401 in preflight)
My auth file looks like this. Aside: this seems confusing. Turning on auth should secure all endpoints by default. I have no idea what's leaking.
Do I have a configuration issue? FYI I tried adding options explicitly - didn't help.
The text was updated successfully, but these errors were encountered: