You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2017/03/04 02:38:45 UTC

[jira] [Updated] (MNG-5585) match server credentials based on server realm

     [ https://issues.apache.org/jira/browse/MNG-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hervé Boutemy updated MNG-5585:
-------------------------------
    Description: 
credentials for repositories are identified based on arbitrary ID. This is error prone and fragile design, especially as there's no way to diagnose which credentials are used (see MNG-5584).

A realm-based server matching would better follow the way HTTP security is defined, and could be easily used for other protocols based (for sample) on domain name.

{code:xml}<server>
     <id>xxx</id>  
     <realm>[optional protocol://]repo.acme.com</realm>
    ..
</server>{code}



  was:
credentials for repositories are identified based on arbitrary ID. This is error prone and fragile design, especially as there's no way to diagnose which credentials are used (see MNG-5584).

A realm-based server matching would better follow the way HTTP security is defined, and could be easily used for other protocols based (for sample) on domain name.

<server>
     <id>xxx</id>  
     <realm>[optional protocol://]repo.acme.com</realm>
    ..
</server>




> match server credentials based on server realm
> ----------------------------------------------
>
>                 Key: MNG-5585
>                 URL: https://issues.apache.org/jira/browse/MNG-5585
>             Project: Maven
>          Issue Type: Improvement
>          Components: Settings
>    Affects Versions: 3.x / Backlog
>            Reporter: nicolas de loof
>
> credentials for repositories are identified based on arbitrary ID. This is error prone and fragile design, especially as there's no way to diagnose which credentials are used (see MNG-5584).
> A realm-based server matching would better follow the way HTTP security is defined, and could be easily used for other protocols based (for sample) on domain name.
> {code:xml}<server>
>      <id>xxx</id>  
>      <realm>[optional protocol://]repo.acme.com</realm>
>     ..
> </server>{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)