felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Miroslav Šulc (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (FELIX-651) Access to password protected OBR
Date Mon, 26 Mar 2012 20:14:28 GMT

    [ https://issues.apache.org/jira/browse/FELIX-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238764#comment-13238764

Miroslav Šulc commented on FELIX-651:

are there any plans to add support for password protected obr? i'd like to be able to plug
private obr repository to web console bundle repository, install some packages and then remove
the obr, this all done in public network.
> Access to password protected OBR
> --------------------------------
>                 Key: FELIX-651
>                 URL: https://issues.apache.org/jira/browse/FELIX-651
>             Project: Felix
>          Issue Type: Improvement
>          Components: Bundle Repository (OBR)
>            Reporter: Remco Poortinga - van Wijnen
>            Priority: Trivial
>         Attachments: UrlEmbeddedCredentialsAuthenticator.java
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
> For a project I would like to configure a 'private' OBR (somewhat against the federated
idea of OBR I guess, but anyway). In other words: username/password protected access. Https
OBR are possible, but I have no idea if there is an 'official' way (from Felix' point of view)
for specifying credentials for the specified OBR URLs.
> Just to see whether it would work I created a test version where username/password can
be specified in a RFC1738 compliant way, e.g. https://user:password@server:port/rest and added
an Authenticator to the bundlerepository bundle, which gets the username/password from the
URL if it is set (see http://java.sun.com/javase/6/docs/api/java/net/URL.html#getUserInfo()).
> This seems to work OK; would this be interesting for others as well?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message