It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,830

question asked: Dec 23 '10, 10:06 a.m.
question was seen: 5,939 times
last updated: Dec 23 '10, 10:06 a.m.

Related questions

LDAP authentication with nested groups ?

0
Michael Sternberg (81●8●1) | asked Dec 23 '10, 10:06 a.m.
Hello everybody.

I've configured RTC 3.0 server to use LDAP as users repository (LDAP4Newbies and Users Guide). We're using IBM BluePages as LDAP provider. I discovered that:
  1. Users, that belong to subgroup of a group, that was mapped as "JazzUsers", are not authenticated.
  2. Also, the same users are not automatically imported when LDAP nightly syncronization process is running
Is it known fact that RTC doesn't supports LDAP authentication of nested groups and if yes - which project (Jazz foundation or RTC) and which category should I use when opening a defect ?

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Dec 26 '10, 7:38 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
This is work item 59463. It is currently not in-plan, so please add a
comment to indicate your interest/support.

Cheers,
Geoff

On 12/26/2010 6:12 PM, mishka wrote:
Hello everybody.

I've configured RTC 3.0 server to use LDAP as users repository
(LDAP4Newbies
and
Users
Guide). We're using IBM BluePages as LDAP provider. I discovered
that:
  • Users, that belong to subgroup of a
    group, that was mapped as "JazzUsers", are
    not authenticated.
  • Also, the same users are not automatically imported when
    LDAP nightly syncronization process is runningIs
    it known fact that RTC doesn't supports LDAP authentication of nested
    groups and if yes - which project (Jazz foundation or RTC) and which
    category should I use when opening a defect ?
    		•

    Your answer

    Register or to post your answer.


    Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.