-
Notifications
You must be signed in to change notification settings - Fork 12
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
The REST v2 API ignores a user's admin attribute in authorization #37
Comments
@bcarlin I will need more time for this one, since I did not look into REST V2. |
It turns out that previous fix (Business fix, in particular ROLE) resolves this issue. I'm currently testing it. |
fredericBregier
added a commit
to fredericBregier/Waarp-All
that referenced
this issue
May 22, 2020
- Already fix in previous commit but add some tests to prevent regression - Also extra missing fix bad usage of initialization of Transfer in Rest V2 Fix issue waarp#37
See #40 |
fredericBregier
added a commit
to fredericBregier/Waarp-All
that referenced
this issue
May 27, 2020
- Already fix in previous commit but add some tests to prevent regression - Also extra missing fix bad usage of initialization of Transfer in Rest V2 Fix issue waarp#37
fredericBregier
added a commit
to fredericBregier/Waarp-All
that referenced
this issue
May 27, 2020
- Additional fixes on REST V2 - Add some tests to prevent regression - Also extra missing fix bad usage of initialization of Transfer in Rest V2 Fix issue waarp#37
Additional fixes in PR |
fredericBregier
added a commit
to fredericBregier/Waarp-All
that referenced
this issue
May 27, 2020
- Additional fixes on REST V2 - Add some tests to prevent regression - Also extra missing fix bad usage of initialization of Transfer in Rest V2 - Add fix on Proxy Rest test Fix issue waarp#37
fredericBregier
added a commit
to fredericBregier/Waarp-All
that referenced
this issue
May 27, 2020
- Additional fixes on REST V2 - Add some tests to prevent regression - Also extra missing fix bad usage of initialization of Transfer in Rest V2 - Add fix on Proxy Rest test - Minor fix on default TCP (TCP_NODELAY set to false) Fix issue waarp#37
Fixes finalized |
fredericBregier
added a commit
to fredericBregier/Waarp-All
that referenced
this issue
May 28, 2020
- Additional fixes on REST V2 - Add some tests to prevent regression - Also extra missing fix bad usage of initialization of Transfer in Rest V2 - Add fix on Proxy Rest test - Minor fix on default TCP (TCP_NODELAY set to false) Fix issue waarp#37
fredericBregier
added a commit
to fredericBregier/Waarp-All
that referenced
this issue
May 28, 2020
- Additional fixes on REST V2 - Add some tests to prevent regression - Also extra missing fix bad usage of initialization of Transfer in Rest V2 - Add fix on Proxy Rest test - Minor fix on default TCP (TCP_NODELAY set to false) Fix issue waarp#37
fredericBregier
added a commit
that referenced
this issue
May 28, 2020
- Additional fixes on REST V2 - Add some tests to prevent regression - Also extra missing fix bad usage of initialization of Transfer in Rest V2 - Add fix on Proxy Rest test - Minor fix on default TCP (TCP_NODELAY set to false) Fix issue #37
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the REST v1 API, a user with
admin = true
as a de factoFULLADMIN
role.However, in the REST v2 API, a user with
admin = true
as a de factoNOACCESS
role.The text was updated successfully, but these errors were encountered: