Hello,
Not sure if this is already possible (or indeed wanted), but I couldn't
find anything on the web or the mail archives about this.
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 prot
Hello,
Not sure if this is already possible (or indeed wanted), but I couldn't
find anything on the web or the mail archives about this.
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 prot
Interesting. You should attach all code patches to a Felix JIRA issue
for consideration for inclusion:
http://cwiki.apache.org/FELIX/issue-tracking.html
If people think this would be a useful addition, it is likely we could
include it. Make sure to tick the "grant" box when you fill out the
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
Which may be a good thing (then works for all URLs throughout Felix), or a bad
thing (might cause other issues? Not sure which, I'm not really familiar with
the internals of Felix).
> Access to password protected OBR
>
>
> Key: F
olution might be to use Apache HttpComponents to be able to fully
control credentials processing and to use user/password setting out of band of
the URL.
> Access to password protected OBR
>
>
> Key: FELIX-651
> URL: htt
word 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
>
>
>
