[
https://issues.apache.org/jira/browse/BROOKLYN-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736604#comment-14736604
]
ASF GitHub Bot commented on BROOKLYN-169:
-----------------------------------------
Github user aledsage commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/877#issuecomment-138863584
Also see https://github.com/apache/incubator-brooklyn/pull/881, which had
`CreateUserPolicyWithEntityLiveTest` but was then closed. However, how does
that test differ from `CreateUserPolicyLiveTest`? Is it different enough to
justify adding that extra test? And if we do include it, then please see the
assertions in `CreateUserPolicyLiveTest` which are better than just checking
that no exceptions were thrown.
> CreateUserPolicy always resets the password
> -------------------------------------------
>
> Key: BROOKLYN-169
> URL: https://issues.apache.org/jira/browse/BROOKLYN-169
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.7.0, 0.8.0-SNAPSHOT
> Environment: Linux
> Reporter: Yavor Yanchev
> Fix For: 0.8.0-SNAPSHOT
>
>
> CreateUserPolicy always resets the password for the "user".
> Even when it is used in conjunction with BYON location.
> Brooklyn fails to finish BYON location deployments when byon user's password
> is changed.
> Currently, the byon user (used to create the new "user") gets password reset
> to the newely generated password. In this case all subsequent commands will
> fail, e.g. grantSudo.
> We need a new parameter (which can be set by the user) to determine when
> password to be reset, e.g. CreateUserPolicy is used in combination with BYON
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
