You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Olivier Lamy <ol...@apache.org> on 2013/04/20 15:15:25 UTC

Re: Releasing 1.4-M4

Sorry again for delay.
I will start slowly the release (redback-components/redback-core then archiva)

2013/3/6 Olivier Lamy <ol...@apache.org>:
> So apologize for delay.
> But for personal reasons, I will delay the release for early/mid april
> (except if someone beat me)
> I will concentrate my efforts to finish ldap integration (in fact
> chaining of redback providers: jdo + ldap ). Currently it works I just
> have to finish the screen to map one ldap group to n archiva roles.
>
> If someone else have a bit of time to take care of some of issues
> scheduled for 1.4-M4 that could be great :-).
>
> Cheers !
> --
> Olivier
>
> 2013/2/8 Deng Ching <oc...@apache.org>:
>> Looks good, I'll have to try it out here. Thanks Olivier!
>>
>> -Deng
>>
>> On Wed, Feb 6, 2013 at 7:01 PM, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> Apologize for delay (some other stuff to do recently)
>>> Most of ldap mapping is implemented ( ldap group -> n archiva roles).
>>> Can be done via file security.properties (see
>>> http://archiva.apache.org/redback/configuration.html )
>>>
>>> ldap.config.groups.class= object class for groups (default:
>>> groupOfUniqueNames)
>>> ldap.config.groups.base.dn= basedn for groups, dn with list of groups
>>> ( dc=archiva,dc=apache,dc=org ) (if empty default will be
>>> ldap.config.base.dn)
>>> ldap.config.groups.role.*(ldap group)=*(roles) (mapping ldap group -
>>> redback roles comma separated) (example:
>>> ldap.config.groups.role.archiva-admin=Archiva System Administrator,
>>> Foo)
>>> ldap.config.writable=true/false will write datas to ldap (default false)
>>> ldap.config.groups.use.rolename=true/false will create groups in ldap
>>> with default role if no group-role mapping found (default false)
>>> ldap.config.user.attribute= attribute name to use for user (default uid=)
>>>
>>> Note the new ldap.config.writable this mean is possible to activate
>>> write to ldap (for groups creation and users)
>>>
>>> Now (I hope in the coming days) I will add a ui screen to map groups to n
>>> roles.
>>>
>>> I'd like to add some changes (but probably for a next release). This
>>> means be able to fully remove the database use as currently the
>>> roles/permissions (redback model) still need a database.
>>>
>>> Any comments are welcome :-)
>>>
>>>
>>> 2013/1/2 Olivier Lamy <ol...@apache.org>:
>>> > So finally I will implement that for 1.4-M4 :-)
>>> > That sounds to be a nice feature to have.
>>> > The idea will be to add some configuration mapping between ldap group
>>> > and archiva/redback roles.
>>> >
>>> > 2012/12/21 Olivier Lamy <ol...@apache.org>:
>>> >> 2012/12/21 Brett Porter <br...@apache.org>:
>>> >>>
>>> >>> On 21/12/2012, at 7:39 PM, Olivier Lamy <ol...@apache.org> wrote:
>>> >>>
>>> >>>> Note something I'd like to add is to be able to use only ldap
>>> >>>> (including for roles).
>>> >>>> But probably not yet for this release, I have to think which ldap
>>> >>>> attributes to use for role mapping (and a couple of other things :-)
>>> >>>> ).
>>> >>>> Such feature makes sense ?
>>> >>>
>>> >>> I'm not sure you'll get the granularity of the resources/permissions
>>> that you want without overly-polluting LDAP or unless you limit it to the
>>> global roles.
>>> >>>
>>> >>> Probably the better way to approach it is to add support for groups
>>> (mapped onto LDAP) that can be assigned to roles (still stored in
>>> Archiva/Redback).
>>> >>
>>> >> Sounds good to do such mapping.
>>> >> But for next release :-)
>>> >>
>>> >>>
>>> >>> - Brett
>>> >>>
>>> >>> --
>>> >>> Brett Porter
>>> >>> brett@apache.org
>>> >>> http://brettporter.wordpress.com/
>>> >>> http://au.linkedin.com/in/brettporter
>>> >>> http://twitter.com/brettporter
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Olivier Lamy
>>> >> Talend: http://coders.talend.com
>>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> >
>>> >
>>> >
>>> > --
>>> > Olivier Lamy
>>> > Talend: http://coders.talend.com
>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>
>>
>>
>> --
>> Maria Odea Ching | oching@apache.org | http://www.linkedin.com/in/oching
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Releasing 1.4-M4

Posted by Deng Ching-Mallete <oc...@apache.org>.
On Wed, May 1, 2013 at 6:43 PM, Olivier Lamy <ol...@apache.org> wrote:

> 2013/5/1 Deng Ching-Mallete <od...@gmail.com>:
> > I'd like to add more audit logging (info, debug level) for easier
> debugging
> > & trouble shooting for final 1.4.0 :)
> wdym exactly ? more debug statement in various classes ? (maybe create
> some markers to help ? managed-repository, artifacts-read etc...)
>

Yep, more debug statements in various classes. I'll add more notes in the
ticket I filed for this.


>
> >
> > We can go through the tickets in 1.4-M5 and 1.4 buckets in JIRA and
> review
> > each one then see if they're still applicable and/or critical for 1.4
> > final. Olivier, I can help you sift through them then we can discuss on
> the
> > list which ones to keep in or out of 1.4?
> sure
>

Cool :-)

-Deng


> >
> > Thanks,
> > Deng
> >
> >
> > On Mon, Apr 22, 2013 at 8:04 PM, Sascha Vogt <sa...@gmail.com>
> wrote:
> >
> >> Hi Olivier,
> >>
> >> what I meant was, focusing on getting a 1.4.0 out "fast", so remove
> >> everything not absolutley necessary for a .0 release and move it to a
> >> 1.4.1.
> >>
> >> I personally don't want anything more in a .0 - so from my point only
> >> stabilizing and UI bugfixes (if there are any more issues, as said, will
> >> check again after M4 is released) would be "needed".
> >>
> >> But obviously I don't have any say in this ;) that's why I asked, what
> >> the timeline from the devs point of view is :)
> >>
> >> Greetings
> >> -Sascha-
> >>
> >> Am 22.04.2013 13:05, schrieb Olivier Lamy:
> >> > Hi,
> >> > Currently our instance @apache is broken (my fault !! I fail an os
> >> > upgrade). So I don't know when I will be able to start the release.
> >> >
> >> > Regarding roadmap, I added some new features for 1.4-M4 (regarding
> >> > users/roles chaining) so I hope not too much bugs.
> >> > IMHO a 1.4-M5 is possible with new fixes.
> >> > Regarding what will be in the final 1.4.0, I have no idea maybe add a
> >> > comment on what you will be happy to have in the release. (and better
> >> > with a patch :P )
> >> >
> >> > BTW sure after 1.4.0, I hope we will have 1.4.1 etc...
> >> >
> >> >
> >> >
> >> > 2013/4/22 Sascha Vogt <sa...@gmail.com>:
> >> >> Hi all,
> >> >>
> >> >> great to see progress on the 1.4 front ;)
> >> >>
> >> >> A general question: How is the roadmap for a 1.4 final release? I
> >> >> currently see 89 issues in Jira "targeted" for either M5 or 1.4. Are
> >> >> these all considered to be critical for a 1.4 final?
> >> >>
> >> >> The main point for asking is, that we're currently at 1.3.6 and have
> >> >> quite a few pain points :) most of them are already fixed in 1.4
> though
> >> >> a few nasty UI issues prevent us currently from upgrading (though I
> must
> >> >> admit I haven't looked at the latest M4 SNAPSHOT, will definitely try
> >> >> the M4 release).
> >> >>
> >> >> As 1.4 makes huge improvements - wouldn't it be possible to figure
> out
> >> >> what is critical to be in a 1.4.0 release, get that ready and out and
> >> >> then improving it with 1.4.1 and so on?
> >> >>
> >> >> Greetings
> >> >> -Sascha-
> >> >>
> >> >> Am 21.04.2013 11:37, schrieb Chris Graham:
> >> >>> :-)
> >> >>>
> >> >>> I'll be sure to put it through it's paces!
> >> >>>
> >> >>> -Chris
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Sat, Apr 20, 2013 at 11:15 PM, Olivier Lamy <ol...@apache.org>
> >> wrote:
> >> >>>
> >> >>>> Sorry again for delay.
> >> >>>> I will start slowly the release (redback-components/redback-core
> then
> >> >>>> archiva)
> >>
> >>
> >
> >
> > --
> > Maria Odea "Deng" Ching-Mallete | oching@apache.org |
> > http://www.linkedin.com/in/oching
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>



-- 
Maria Odea "Deng" Ching-Mallete | oching@apache.org |
http://www.linkedin.com/in/oching

Re: Releasing 1.4-M4

Posted by Olivier Lamy <ol...@apache.org>.
2013/5/1 Deng Ching-Mallete <od...@gmail.com>:
> I'd like to add more audit logging (info, debug level) for easier debugging
> & trouble shooting for final 1.4.0 :)
wdym exactly ? more debug statement in various classes ? (maybe create
some markers to help ? managed-repository, artifacts-read etc...)

>
> We can go through the tickets in 1.4-M5 and 1.4 buckets in JIRA and review
> each one then see if they're still applicable and/or critical for 1.4
> final. Olivier, I can help you sift through them then we can discuss on the
> list which ones to keep in or out of 1.4?
sure
>
> Thanks,
> Deng
>
>
> On Mon, Apr 22, 2013 at 8:04 PM, Sascha Vogt <sa...@gmail.com> wrote:
>
>> Hi Olivier,
>>
>> what I meant was, focusing on getting a 1.4.0 out "fast", so remove
>> everything not absolutley necessary for a .0 release and move it to a
>> 1.4.1.
>>
>> I personally don't want anything more in a .0 - so from my point only
>> stabilizing and UI bugfixes (if there are any more issues, as said, will
>> check again after M4 is released) would be "needed".
>>
>> But obviously I don't have any say in this ;) that's why I asked, what
>> the timeline from the devs point of view is :)
>>
>> Greetings
>> -Sascha-
>>
>> Am 22.04.2013 13:05, schrieb Olivier Lamy:
>> > Hi,
>> > Currently our instance @apache is broken (my fault !! I fail an os
>> > upgrade). So I don't know when I will be able to start the release.
>> >
>> > Regarding roadmap, I added some new features for 1.4-M4 (regarding
>> > users/roles chaining) so I hope not too much bugs.
>> > IMHO a 1.4-M5 is possible with new fixes.
>> > Regarding what will be in the final 1.4.0, I have no idea maybe add a
>> > comment on what you will be happy to have in the release. (and better
>> > with a patch :P )
>> >
>> > BTW sure after 1.4.0, I hope we will have 1.4.1 etc...
>> >
>> >
>> >
>> > 2013/4/22 Sascha Vogt <sa...@gmail.com>:
>> >> Hi all,
>> >>
>> >> great to see progress on the 1.4 front ;)
>> >>
>> >> A general question: How is the roadmap for a 1.4 final release? I
>> >> currently see 89 issues in Jira "targeted" for either M5 or 1.4. Are
>> >> these all considered to be critical for a 1.4 final?
>> >>
>> >> The main point for asking is, that we're currently at 1.3.6 and have
>> >> quite a few pain points :) most of them are already fixed in 1.4 though
>> >> a few nasty UI issues prevent us currently from upgrading (though I must
>> >> admit I haven't looked at the latest M4 SNAPSHOT, will definitely try
>> >> the M4 release).
>> >>
>> >> As 1.4 makes huge improvements - wouldn't it be possible to figure out
>> >> what is critical to be in a 1.4.0 release, get that ready and out and
>> >> then improving it with 1.4.1 and so on?
>> >>
>> >> Greetings
>> >> -Sascha-
>> >>
>> >> Am 21.04.2013 11:37, schrieb Chris Graham:
>> >>> :-)
>> >>>
>> >>> I'll be sure to put it through it's paces!
>> >>>
>> >>> -Chris
>> >>>
>> >>>
>> >>>
>> >>> On Sat, Apr 20, 2013 at 11:15 PM, Olivier Lamy <ol...@apache.org>
>> wrote:
>> >>>
>> >>>> Sorry again for delay.
>> >>>> I will start slowly the release (redback-components/redback-core then
>> >>>> archiva)
>>
>>
>
>
> --
> Maria Odea "Deng" Ching-Mallete | oching@apache.org |
> http://www.linkedin.com/in/oching



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Releasing 1.4-M4

Posted by Deng Ching-Mallete <od...@gmail.com>.
I'd like to add more audit logging (info, debug level) for easier debugging
& trouble shooting for final 1.4.0 :)

We can go through the tickets in 1.4-M5 and 1.4 buckets in JIRA and review
each one then see if they're still applicable and/or critical for 1.4
final. Olivier, I can help you sift through them then we can discuss on the
list which ones to keep in or out of 1.4?

Thanks,
Deng


On Mon, Apr 22, 2013 at 8:04 PM, Sascha Vogt <sa...@gmail.com> wrote:

> Hi Olivier,
>
> what I meant was, focusing on getting a 1.4.0 out "fast", so remove
> everything not absolutley necessary for a .0 release and move it to a
> 1.4.1.
>
> I personally don't want anything more in a .0 - so from my point only
> stabilizing and UI bugfixes (if there are any more issues, as said, will
> check again after M4 is released) would be "needed".
>
> But obviously I don't have any say in this ;) that's why I asked, what
> the timeline from the devs point of view is :)
>
> Greetings
> -Sascha-
>
> Am 22.04.2013 13:05, schrieb Olivier Lamy:
> > Hi,
> > Currently our instance @apache is broken (my fault !! I fail an os
> > upgrade). So I don't know when I will be able to start the release.
> >
> > Regarding roadmap, I added some new features for 1.4-M4 (regarding
> > users/roles chaining) so I hope not too much bugs.
> > IMHO a 1.4-M5 is possible with new fixes.
> > Regarding what will be in the final 1.4.0, I have no idea maybe add a
> > comment on what you will be happy to have in the release. (and better
> > with a patch :P )
> >
> > BTW sure after 1.4.0, I hope we will have 1.4.1 etc...
> >
> >
> >
> > 2013/4/22 Sascha Vogt <sa...@gmail.com>:
> >> Hi all,
> >>
> >> great to see progress on the 1.4 front ;)
> >>
> >> A general question: How is the roadmap for a 1.4 final release? I
> >> currently see 89 issues in Jira "targeted" for either M5 or 1.4. Are
> >> these all considered to be critical for a 1.4 final?
> >>
> >> The main point for asking is, that we're currently at 1.3.6 and have
> >> quite a few pain points :) most of them are already fixed in 1.4 though
> >> a few nasty UI issues prevent us currently from upgrading (though I must
> >> admit I haven't looked at the latest M4 SNAPSHOT, will definitely try
> >> the M4 release).
> >>
> >> As 1.4 makes huge improvements - wouldn't it be possible to figure out
> >> what is critical to be in a 1.4.0 release, get that ready and out and
> >> then improving it with 1.4.1 and so on?
> >>
> >> Greetings
> >> -Sascha-
> >>
> >> Am 21.04.2013 11:37, schrieb Chris Graham:
> >>> :-)
> >>>
> >>> I'll be sure to put it through it's paces!
> >>>
> >>> -Chris
> >>>
> >>>
> >>>
> >>> On Sat, Apr 20, 2013 at 11:15 PM, Olivier Lamy <ol...@apache.org>
> wrote:
> >>>
> >>>> Sorry again for delay.
> >>>> I will start slowly the release (redback-components/redback-core then
> >>>> archiva)
>
>


-- 
Maria Odea "Deng" Ching-Mallete | oching@apache.org |
http://www.linkedin.com/in/oching

Re: Releasing 1.4-M4

Posted by Sascha Vogt <sa...@gmail.com>.
Hi Olivier,

what I meant was, focusing on getting a 1.4.0 out "fast", so remove
everything not absolutley necessary for a .0 release and move it to a 1.4.1.

I personally don't want anything more in a .0 - so from my point only
stabilizing and UI bugfixes (if there are any more issues, as said, will
check again after M4 is released) would be "needed".

But obviously I don't have any say in this ;) that's why I asked, what
the timeline from the devs point of view is :)

Greetings
-Sascha-

Am 22.04.2013 13:05, schrieb Olivier Lamy:
> Hi,
> Currently our instance @apache is broken (my fault !! I fail an os
> upgrade). So I don't know when I will be able to start the release.
> 
> Regarding roadmap, I added some new features for 1.4-M4 (regarding
> users/roles chaining) so I hope not too much bugs.
> IMHO a 1.4-M5 is possible with new fixes.
> Regarding what will be in the final 1.4.0, I have no idea maybe add a
> comment on what you will be happy to have in the release. (and better
> with a patch :P )
> 
> BTW sure after 1.4.0, I hope we will have 1.4.1 etc...
> 
> 
> 
> 2013/4/22 Sascha Vogt <sa...@gmail.com>:
>> Hi all,
>>
>> great to see progress on the 1.4 front ;)
>>
>> A general question: How is the roadmap for a 1.4 final release? I
>> currently see 89 issues in Jira "targeted" for either M5 or 1.4. Are
>> these all considered to be critical for a 1.4 final?
>>
>> The main point for asking is, that we're currently at 1.3.6 and have
>> quite a few pain points :) most of them are already fixed in 1.4 though
>> a few nasty UI issues prevent us currently from upgrading (though I must
>> admit I haven't looked at the latest M4 SNAPSHOT, will definitely try
>> the M4 release).
>>
>> As 1.4 makes huge improvements - wouldn't it be possible to figure out
>> what is critical to be in a 1.4.0 release, get that ready and out and
>> then improving it with 1.4.1 and so on?
>>
>> Greetings
>> -Sascha-
>>
>> Am 21.04.2013 11:37, schrieb Chris Graham:
>>> :-)
>>>
>>> I'll be sure to put it through it's paces!
>>>
>>> -Chris
>>>
>>>
>>>
>>> On Sat, Apr 20, 2013 at 11:15 PM, Olivier Lamy <ol...@apache.org> wrote:
>>>
>>>> Sorry again for delay.
>>>> I will start slowly the release (redback-components/redback-core then
>>>> archiva)

Re: Releasing 1.4-M4

Posted by Olivier Lamy <ol...@apache.org>.
Hi,
Currently our instance @apache is broken (my fault !! I fail an os
upgrade). So I don't know when I will be able to start the release.

Regarding roadmap, I added some new features for 1.4-M4 (regarding
users/roles chaining) so I hope not too much bugs.
IMHO a 1.4-M5 is possible with new fixes.
Regarding what will be in the final 1.4.0, I have no idea maybe add a
comment on what you will be happy to have in the release. (and better
with a patch :P )

BTW sure after 1.4.0, I hope we will have 1.4.1 etc...



2013/4/22 Sascha Vogt <sa...@gmail.com>:
> Hi all,
>
> great to see progress on the 1.4 front ;)
>
> A general question: How is the roadmap for a 1.4 final release? I
> currently see 89 issues in Jira "targeted" for either M5 or 1.4. Are
> these all considered to be critical for a 1.4 final?
>
> The main point for asking is, that we're currently at 1.3.6 and have
> quite a few pain points :) most of them are already fixed in 1.4 though
> a few nasty UI issues prevent us currently from upgrading (though I must
> admit I haven't looked at the latest M4 SNAPSHOT, will definitely try
> the M4 release).
>
> As 1.4 makes huge improvements - wouldn't it be possible to figure out
> what is critical to be in a 1.4.0 release, get that ready and out and
> then improving it with 1.4.1 and so on?
>
> Greetings
> -Sascha-
>
> Am 21.04.2013 11:37, schrieb Chris Graham:
>> :-)
>>
>> I'll be sure to put it through it's paces!
>>
>> -Chris
>>
>>
>>
>> On Sat, Apr 20, 2013 at 11:15 PM, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> Sorry again for delay.
>>> I will start slowly the release (redback-components/redback-core then
>>> archiva)
>



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Releasing 1.4-M4

Posted by Sascha Vogt <sa...@gmail.com>.
Hi all,

great to see progress on the 1.4 front ;)

A general question: How is the roadmap for a 1.4 final release? I
currently see 89 issues in Jira "targeted" for either M5 or 1.4. Are
these all considered to be critical for a 1.4 final?

The main point for asking is, that we're currently at 1.3.6 and have
quite a few pain points :) most of them are already fixed in 1.4 though
a few nasty UI issues prevent us currently from upgrading (though I must
admit I haven't looked at the latest M4 SNAPSHOT, will definitely try
the M4 release).

As 1.4 makes huge improvements - wouldn't it be possible to figure out
what is critical to be in a 1.4.0 release, get that ready and out and
then improving it with 1.4.1 and so on?

Greetings
-Sascha-

Am 21.04.2013 11:37, schrieb Chris Graham:
> :-)
> 
> I'll be sure to put it through it's paces!
> 
> -Chris
> 
> 
> 
> On Sat, Apr 20, 2013 at 11:15 PM, Olivier Lamy <ol...@apache.org> wrote:
> 
>> Sorry again for delay.
>> I will start slowly the release (redback-components/redback-core then
>> archiva)

Re: Releasing 1.4-M4

Posted by Chris Graham <ch...@gmail.com>.
:-)

I'll be sure to put it through it's paces!

-Chris



On Sat, Apr 20, 2013 at 11:15 PM, Olivier Lamy <ol...@apache.org> wrote:

> Sorry again for delay.
> I will start slowly the release (redback-components/redback-core then
> archiva)
>
> 2013/3/6 Olivier Lamy <ol...@apache.org>:
> > So apologize for delay.
> > But for personal reasons, I will delay the release for early/mid april
> > (except if someone beat me)
> > I will concentrate my efforts to finish ldap integration (in fact
> > chaining of redback providers: jdo + ldap ). Currently it works I just
> > have to finish the screen to map one ldap group to n archiva roles.
> >
> > If someone else have a bit of time to take care of some of issues
> > scheduled for 1.4-M4 that could be great :-).
> >
> > Cheers !
> > --
> > Olivier
> >
> > 2013/2/8 Deng Ching <oc...@apache.org>:
> >> Looks good, I'll have to try it out here. Thanks Olivier!
> >>
> >> -Deng
> >>
> >> On Wed, Feb 6, 2013 at 7:01 PM, Olivier Lamy <ol...@apache.org> wrote:
> >>
> >>> Apologize for delay (some other stuff to do recently)
> >>> Most of ldap mapping is implemented ( ldap group -> n archiva roles).
> >>> Can be done via file security.properties (see
> >>> http://archiva.apache.org/redback/configuration.html )
> >>>
> >>> ldap.config.groups.class= object class for groups (default:
> >>> groupOfUniqueNames)
> >>> ldap.config.groups.base.dn= basedn for groups, dn with list of groups
> >>> ( dc=archiva,dc=apache,dc=org ) (if empty default will be
> >>> ldap.config.base.dn)
> >>> ldap.config.groups.role.*(ldap group)=*(roles) (mapping ldap group -
> >>> redback roles comma separated) (example:
> >>> ldap.config.groups.role.archiva-admin=Archiva System Administrator,
> >>> Foo)
> >>> ldap.config.writable=true/false will write datas to ldap (default
> false)
> >>> ldap.config.groups.use.rolename=true/false will create groups in ldap
> >>> with default role if no group-role mapping found (default false)
> >>> ldap.config.user.attribute= attribute name to use for user (default
> uid=)
> >>>
> >>> Note the new ldap.config.writable this mean is possible to activate
> >>> write to ldap (for groups creation and users)
> >>>
> >>> Now (I hope in the coming days) I will add a ui screen to map groups
> to n
> >>> roles.
> >>>
> >>> I'd like to add some changes (but probably for a next release). This
> >>> means be able to fully remove the database use as currently the
> >>> roles/permissions (redback model) still need a database.
> >>>
> >>> Any comments are welcome :-)
> >>>
> >>>
> >>> 2013/1/2 Olivier Lamy <ol...@apache.org>:
> >>> > So finally I will implement that for 1.4-M4 :-)
> >>> > That sounds to be a nice feature to have.
> >>> > The idea will be to add some configuration mapping between ldap group
> >>> > and archiva/redback roles.
> >>> >
> >>> > 2012/12/21 Olivier Lamy <ol...@apache.org>:
> >>> >> 2012/12/21 Brett Porter <br...@apache.org>:
> >>> >>>
> >>> >>> On 21/12/2012, at 7:39 PM, Olivier Lamy <ol...@apache.org> wrote:
> >>> >>>
> >>> >>>> Note something I'd like to add is to be able to use only ldap
> >>> >>>> (including for roles).
> >>> >>>> But probably not yet for this release, I have to think which ldap
> >>> >>>> attributes to use for role mapping (and a couple of other things
> :-)
> >>> >>>> ).
> >>> >>>> Such feature makes sense ?
> >>> >>>
> >>> >>> I'm not sure you'll get the granularity of the
> resources/permissions
> >>> that you want without overly-polluting LDAP or unless you limit it to
> the
> >>> global roles.
> >>> >>>
> >>> >>> Probably the better way to approach it is to add support for groups
> >>> (mapped onto LDAP) that can be assigned to roles (still stored in
> >>> Archiva/Redback).
> >>> >>
> >>> >> Sounds good to do such mapping.
> >>> >> But for next release :-)
> >>> >>
> >>> >>>
> >>> >>> - Brett
> >>> >>>
> >>> >>> --
> >>> >>> Brett Porter
> >>> >>> brett@apache.org
> >>> >>> http://brettporter.wordpress.com/
> >>> >>> http://au.linkedin.com/in/brettporter
> >>> >>> http://twitter.com/brettporter
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>
> >>> >>
> >>> >>
> >>> >> --
> >>> >> Olivier Lamy
> >>> >> Talend: http://coders.talend.com
> >>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Olivier Lamy
> >>> > Talend: http://coders.talend.com
> >>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>>
> >>>
> >>>
> >>> --
> >>> Olivier Lamy
> >>> Talend: http://coders.talend.com
> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>>
> >>
> >>
> >>
> >> --
> >> Maria Odea Ching | oching@apache.org |
> http://www.linkedin.com/in/oching
> >
> >
> >
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>