Skip to content
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

Artifacts managemement #95

Open
zoevas opened this issue Jul 9, 2021 · 0 comments
Open

Artifacts managemement #95

zoevas opened this issue Jul 9, 2021 · 0 comments

Comments

@zoevas
Copy link
Collaborator

zoevas commented Jul 9, 2021

Presentation: https://docs.google.com/presentation/d/1FhA14V1nGRfxlT_MU7-W58jhKAkNchw1f_T9QpqgKg4/edit#slide=id.ge29738600c_0_8

  • Non-text artifacts
    We should solve the issue since the content is broken.
    IDE will send the artifact encoded in base64. In such a way characters will be encoded into ASCII characters.
    Reasoner should decode the file and save it to KB. When the file is requested, we should check if tomcat encodes it automatically.

  • Replication/duplication of the data in the Reasoner should be avoided
    Right now, each time /aadm for getting the json is called, new files for the artifacts are created.

  • Fixing Unrestricted access to the artifacts - add authentication
    The files should be secured. When the url is clicked, http://..../Ansibles/vfvdfdfgdgd
    then a service from the Reasoner could be called for checking a token, and verify if the user has access to the file.
    For the RMs should be role-based because RMs are shared among many users.
    401 error should be sent to the user when no access is allowed.

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

No branches or pull requests

1 participant