[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15522883#comment-15522883
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9489:
--------------------------------------------

Github user pdion891 commented on the issue:

    https://github.com/apache/cloudstack/pull/1684
  
    @abhinandanprateek  I did replace the following 4 settings by the original 
values. But after restarting jetty I'm unable to login, but this time the 
behavior is a bit different, it look like it doesn't try to login, no log or 
message in the UI.
    
    ```
    update configuration set value=null where 
name='user.password.encoders.exclude';
    update configuration set value='SHA256SALT,MD5,LDAP,PLAINTEXT' where 
name='user.authenticators.order';
    update configuration set value=null where 
name='user.authenticators.exclude';
    update configuration set value='SHA256SALT,MD5,LDAP,PLAINTEXT' where 
name='user.password.encoders.order';
    ```
    
    Could it be possible the  authentication order is not followed at the 
login? if the password does not meet ``PBKDF2`` requirement, which is the first 
in the order list of 4.9.0, shouldn't try with the next encoder in the list and 
so on?
    



> When upgrading, Config.java new configuration are not updated.
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9489
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9489
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.6.2, 4.7.1, 4.8.0, 4.9.0
>            Reporter: Pierre-Luc Dion
>            Assignee: Pierre-Luc Dion
>            Priority: Blocker
>
> When Upgrading CloudStack, new configurations (Global Settings) defined in  
> {{server/src/com/cloud/configuration/Config.java}} are not populated.
> This file changed in 4.5 and 4.6 and those configurations are not applied 
> when upgrading to post 4.6.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to