Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

ACL plugin validation bug #486

Closed
taranvohra opened this issue Oct 31, 2019 · 9 comments
Closed

ACL plugin validation bug #486

taranvohra opened this issue Oct 31, 2019 · 9 comments

Comments

@taranvohra
Copy link

I have a defined Service which has a route. I want to add key-auth plugin to that Service. When I try to add Consumer ID, it says field should be null. If i keep it empty, it adds it for all Consumers that exist. Why is it that way? Why can't I have it for specific Consumer?

@taranvohra
Copy link
Author

taranvohra commented Oct 31, 2019

UPDATE
Okay, I figured I needed to add an ACL to the Service and ensure the Consumer is in the group that I want to whitelist. However I keep getting this error when I try to whitelist groups in the ACL plugin.

Screenshot 2019-10-31 at 12 14 42 PM

How is it possible? I have foo in whitelist and nothing in blacklist. This should satisfy the validation rule however it still gives me error!

@taranvohra taranvohra changed the title key-auth on a service being applied to all Consumers ACL plugin validation bug Oct 31, 2019
@taranvohra
Copy link
Author

I opened DevTools and noticed even though I am providing foo to whitelist, the config object in the request is EMPTY!
image

@alvindaiyan
Copy link

I encountered the same issue, can anyone help?

@pantsel
Copy link
Owner

pantsel commented Nov 11, 2019

Guys, did you press enter after typing the value in the whitelist? There's a chip component handling array like structures.

@taranvohra
Copy link
Author

@pantsel yes I did. Have a re look at this screenshot. foo is entered (chip is there) but when I submit, I still get an error.

67925067-4293c900-fbd8-11e9-8eb7-a34ccb1324e4

@pantsel
Copy link
Owner

pantsel commented Nov 11, 2019

What version of Konga are you using?

@alvindaiyan
Copy link

I'm using the next version from Dockerhub

@taranvohra
Copy link
Author

next version from DockerHub

@pantsel
Copy link
Owner

pantsel commented Nov 16, 2019

Fixed the bug on next. Doing some extra tests and moving it to prod

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants