[
https://issues.apache.org/jira/browse/CLOUDSTACK-9099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076260#comment-15076260
]
ASF GitHub Bot commented on CLOUDSTACK-9099:
--------------------------------------------
Github user kansal commented on the pull request:
https://github.com/apache/cloudstack/pull/1152#issuecomment-168295517
@DaanHoogland Agreed with that point. But its not only about the testing.
I'm sure many people will be using it in their own integration. I think we
should not change the response immediately like this without informing or
making a noise about it. And it is because of this concern only, I added a flag
for enabling/disabling the secret key in response.
> SecretKey is returned from the APIs
> -----------------------------------
>
> Key: CLOUDSTACK-9099
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9099
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Kshitij Kansal
> Assignee: Kshitij Kansal
>
> The sercreKey parameter is returned from the following APIs:
> createAccount
> createUser
> disableAccount
> disableUser
> enableAccount
> enableUser
> listAccounts
> listUsers
> lockAccount
> lockUser
> registerUserKeys
> updateAccount
> updateUser
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
