GET /api/v3_0/assets/public should ask for token authentication

[nhoening]

... as it's meant to be used via JSON

[nhoening]

Does this require a changelof entry?

[coveralls]

Pull Request Test Coverage Report for Build 4807223105

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 64.812%

---

Totals
Change from base Build 4787293963:	0.0%
Covered Lines:	7082
Relevant Lines:	10171

---

💛 - Coveralls

[GustaafL]

Looks good. I checked if the frontend has any dependencies on this that require changes but I believe it doesn't. Everything also still works.

[Flix6x]

A big UX difference between using those decorators is that @login_required leads to forwarding the agent to the login page, whereas @auth_token_required leads to returning a "unauthenticated" JSON message. In other words, I would classify this as a bug, and would recommend adding a changelog entry.

[Flix6x]

Idea for letting all API views subclass APIView, and letting all UI views subclass UIView, defined as follows:

class APIView(FlaskView):
    trailing_slash = False
    decorators = [auth_required()]


class UIView(FlaskView):
    decorators = [login_required()]

[nhoening]

Nice. But this further entrenches the use of Flask-Classful. On the PR there which blocks us, people are asking officially if the project is abandoned.