We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A solution that I can think of: Right now the url is directly pointing to the folder in the tomcat server with the file name. eg http://160.40.52.200:8084/Ansibles/6fb0d4b1-0e0e-4d9d-a957-5f2b7436cad7 So I imagine the implementation as a separate web service that authenticates the user before accessing the file e.g. /artifact_file?file_name=<> and the token to be sent in the header of the request thus, in the aadm json the url will be like http://160.40.52.200:8084/reasoner-api/v0.6/artifact_file?file_name=<>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A solution that I can think of:
Right now the url is directly pointing to the folder in the tomcat server with the file name.
eg http://160.40.52.200:8084/Ansibles/6fb0d4b1-0e0e-4d9d-a957-5f2b7436cad7
So I imagine the implementation as a separate web service that authenticates the user before accessing the file e.g. /artifact_file?file_name=<> and the token to be sent in the header of the request
thus, in the aadm json the url will be like http://160.40.52.200:8084/reasoner-api/v0.6/artifact_file?file_name=<>
The text was updated successfully, but these errors were encountered: