OlegChuev opened a new issue, #8299:
URL: https://github.com/apache/cloudstack/issues/8299
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Other
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Console
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
I'm trying to implement access to the VM Console without entering CloudStack
itself. I was able to implement it using the following approach: [link to the
CloudStack developer
documentation](https://docs.cloudstack.apache.org/en/latest/developersguide/dev.html#how-to-sign-an-api-call-with-python).
An example of my request query is as follows:
`/client/console?apikey=XXXXXX&cmd=access&vm=YYYYYY&signature=ZZZZ`
Now, I'm attempting to add signatureVersion and expires parameters, as per
the link above, to the request to add an additional layer of security. However,
it seems that it doesn't work at all. It appears that
`server/src/main/java/com/cloud/servlet/ConsoleProxyServlet.java` lacks the
required functionality. What are your thoughts on adding it somewhere in the
nearest future?
<!-- Explain the problem/feature briefly -->
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
