Problem/Motivation
The json api schema differs in many ways from rest's. JsonAPI schema does not define security or schemes for paths. These lists are not just left blank, but are left off completely. JsonAPI also does not define and root level securityDefinitions in schema either even when core's rest has basic_auth and csrf_token.
Proposed resolution
This should be standardized between rest and jsonapi. we may need to look at how jsonapi handles auth and lists controls valid auth options.
| Comment | File | Size | Author |
|---|---|---|---|
| #18 | 2940412-18-security-definitions.patch | 17.92 KB | richgerdes |
| #18 | 2940412-16-18-interdiff.txt | 897 bytes | richgerdes |
Comments
Comment #2
wim leersFollowing! :)
Comment #3
richgerdesPosting an initial patch for this, so tests can run.
Comment #4
richgerdesI hate functions...
Comment #5
richgerdesComment #6
richgerdesRetest
Comment #7
richgerdesFixed lint error
Comment #8
richgerdesComment #9
richgerdesTaking another pass at the patch.
Comment #10
richgerdesFix invalid index for jsonurls
Comment #11
richgerdesCSRF token needs to be handled differently then other auth collectors since its not one....
Comment #12
richgerdesMatch keys
Comment #14
richgerdesCorrect version of #12.
Comment #16
richgerdesComment #18
richgerdesUsing basic_auth apparently was a bad idea.... It enables nodes for rest, which is not desired and causes tests to fail. We will use csrf for routes then....
Comment #21
richgerdesTests failed as the result of other issues. See #2978465: Tests Fail.... Again.
Comment #22
richgerdesPatch has been committed and pushed.