[jira] [Updated] (MNG-5512) Deploy uses passwords that failed decryption; retries even if login fails
[ https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-5512: Attachment: screenshot-1.png > Deploy uses passwords that failed decryption; retries even if login fails > - > > Key: MNG-5512 > URL: https://issues.apache.org/jira/browse/MNG-5512 > Project: Maven > Issue Type: Bug >Reporter: Sebb >Priority: Major > Fix For: waiting-for-feedback > > Attachments: mng5512.zip, screenshot-1.png > > > [See MDEPLOY-130 which was closed as being an issue in Maven core] > If passwords have been encrypted, deploy fails to notice if the password > decryption failed. > Furthermore, it carries on trying to login even after a login failure. > This is true even if the decryption succeeded but the password was incorrect > or no encryption was used and the password is incorrect. > This is bad as it can result in lockout due to the multiple failed logins - > deploy needs to login several times - and may cause unnecessary work for > system admins. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-5512) Deploy uses passwords that failed decryption; retries even if login fails
[ https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-5512: Fix Version/s: waiting-for-feedback (was: 4.x / Backlog) > Deploy uses passwords that failed decryption; retries even if login fails > - > > Key: MNG-5512 > URL: https://issues.apache.org/jira/browse/MNG-5512 > Project: Maven > Issue Type: Bug >Reporter: Sebb >Priority: Major > Fix For: waiting-for-feedback > > Attachments: mng5512.zip > > > [See MDEPLOY-130 which was closed as being an issue in Maven core] > If passwords have been encrypted, deploy fails to notice if the password > decryption failed. > Furthermore, it carries on trying to login even after a login failure. > This is true even if the decryption succeeded but the password was incorrect > or no encryption was used and the password is incorrect. > This is bad as it can result in lockout due to the multiple failed logins - > deploy needs to login several times - and may cause unnecessary work for > system admins. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MNG-5512) Deploy uses passwords that failed decryption; retries even if login fails
[ https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-5512: -- Fix Version/s: 3.x / Backlog > Deploy uses passwords that failed decryption; retries even if login fails > - > > Key: MNG-5512 > URL: https://issues.apache.org/jira/browse/MNG-5512 > Project: Maven > Issue Type: Bug >Reporter: Sebb >Priority: Major > Fix For: 3.x / Backlog > > Attachments: mng5512.zip > > > [See MDEPLOY-130 which was closed as being an issue in Maven core] > If passwords have been encrypted, deploy fails to notice if the password > decryption failed. > Furthermore, it carries on trying to login even after a login failure. > This is true even if the decryption succeeded but the password was incorrect > or no encryption was used and the password is incorrect. > This is bad as it can result in lockout due to the multiple failed logins - > deploy needs to login several times - and may cause unnecessary work for > system admins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
