[jira] Updated: (WAGONHTTP-13) Allow username and password inputs to http

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/WAGONHTTP-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated WAGONHTTP-13:
----------------------------------

    Fix Version/s: 1.x

I don't understand this request - both providers should already support u/p authn over both basic and digest mode. Are you having a problem with that?

> Allow username and password inputs to http
> ------------------------------------------
>
>                 Key: WAGONHTTP-13
>                 URL: http://jira.codehaus.org/browse/WAGONHTTP-13
>             Project: wagon-http
>          Issue Type: Improvement
>    Affects Versions: 1.0-alpha-6
>         Environment: Any
>            Reporter: Todd Nine
>             Fix For: 1.x
>
>
> Some teams will need repositories available via the web, but will not want their repository publicly available.  They can secure their repository with BASIC or DIGEST authentication.  I can be configured via settings.xml in the following way.
> Server settings
> <server>
> 			<id>maven2</id>
> 			<username>maven</username>
> 			<password>test01</password>			
> 		</server>
> Profile Repositories
> 	<repository>
> 		<releases>
> 			<enabled>true</enabled>
> 		</releases>
> 		<snapshots>
> 			<enabled>true</enabled>
> 		</snapshots>
> 		<id>maven2</id>
> 		<name>Maven repository</name>
> 		<url>
> 			http://maven.mycompany.com
> 		</url>
> 		<layout>default</layout>
> 	</repository>
> If the repository Id matches a server id, then the username and password can be used in both basic and digest mode.  For digest specs, see the RFC here.
> http://www.ietf.org/rfc/rfc2617.txt

-- 
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