You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org> on 2007/11/07 18:40:35 UTC
[jira] Created: (MRM-582) Remote Repositories with empty
and fields shouldn't be created in configuration.
Remote Repositories with empty <username> and <password> fields shouldn't be created in configuration.
------------------------------------------------------------------------------------------------------
Key: MRM-582
URL: http://jira.codehaus.org/browse/MRM-582
Project: Archiva
Issue Type: Bug
Components: system
Affects Versions: 1.0-beta-3
Reporter: Joakim Erdfelt
It is possible for a <remoteRepository> section in the archiva configuration file to be created with an empty <username> and/or <password> fields.
Need to prevent empty/blank username and password fields from being created in the archiva configuration.
Also need to prevent loading blank username and password fields from the archiva configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-582) Remote Repositories with empty
and fields shouldn't be created in configuration.
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joakim Erdfelt closed MRM-582.
------------------------------
Resolution: Fixed
Fixed in archiva/trunk revision 593220.
Implemented on-load cleanup of remote repo username/password (instead of on-save)
Implemented proper check for blank username/password in proxy connectors.
> Remote Repositories with empty <username> and <password> fields shouldn't be created in configuration.
> ------------------------------------------------------------------------------------------------------
>
> Key: MRM-582
> URL: http://jira.codehaus.org/browse/MRM-582
> Project: Archiva
> Issue Type: Bug
> Components: system
> Affects Versions: 1.0-beta-3
> Reporter: Joakim Erdfelt
> Assignee: Joakim Erdfelt
> Fix For: 1.0-beta-4
>
>
> It is possible for a <remoteRepository> section in the archiva configuration file to be created with an empty <username> and/or <password> fields.
> Need to prevent empty/blank username and password fields from being created in the archiva configuration.
> Also need to prevent loading blank username and password fields from the archiva configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-582) Remote Repositories with empty
and fields shouldn't be created in configuration.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-582:
-----------------------------
Fix Version/s: 1.0-beta-4
> Remote Repositories with empty <username> and <password> fields shouldn't be created in configuration.
> ------------------------------------------------------------------------------------------------------
>
> Key: MRM-582
> URL: http://jira.codehaus.org/browse/MRM-582
> Project: Archiva
> Issue Type: Bug
> Components: system
> Affects Versions: 1.0-beta-3
> Reporter: Joakim Erdfelt
> Fix For: 1.0-beta-4
>
>
> It is possible for a <remoteRepository> section in the archiva configuration file to be created with an empty <username> and/or <password> fields.
> Need to prevent empty/blank username and password fields from being created in the archiva configuration.
> Also need to prevent loading blank username and password fields from the archiva configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira