Multiple proxyAuth Path's
-
I know this was discussed previously during the implementation of the
proxyAuthmanifest attribute, but is there a way to disable proxyAuth for multiple paths? For example, in N8N we blocklist/webhookto expose this to the WWW. However, I'm now seeing that there's also a/restthat would be useful to expose for creating Oauth credentials. See here:
-
Just read the docs again and IDK how I got the impression we can do that. Seems like its just one. Ideally we could do something like:
"proxyAuth": { "paths": [ "!/webhook", "!/rest", ] }, -
Right, only one path was implemented since I wanted a use case for having multiple ones before implementing it. Looks like I got a use case now...
-
Right, only one path was implemented since I wanted a use case for having multiple ones before implementing it. Looks like I got a use case now...
-
@girish not to put too much more on your already full plate, but did this request make it onto the roadmap?
@thetomester13 yeah, i don't think it will make it to this release. Will look into it for the next one.
-
@thetomester13 yeah, i don't think it will make it to this release. Will look into it for the next one.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login