RTC, WAS and LDAP
I have successfully installed and deployed RTC 3.0.1 on WAS.
In addition, I have configured the WAS-LDAP integration (from WAS admin console), and the RTC-LDAP integration (from the RTC setup wizard).
The integrations works, as LDAP users are recognized by RTC, and the nightly synchronization was successful, but there's a point I am still missing: why is it necessarty to configure this integration twice?
Wouldn't it be enough to WAS-LDAP integration alone?
In fact, I don't understand the need for an additional RTC-LDAP integration.
In addition, I have configured the WAS-LDAP integration (from WAS admin console), and the RTC-LDAP integration (from the RTC setup wizard).
The integrations works, as LDAP users are recognized by RTC, and the nightly synchronization was successful, but there's a point I am still missing: why is it necessarty to configure this integration twice?
Wouldn't it be enough to WAS-LDAP integration alone?
In fact, I don't understand the need for an additional RTC-LDAP integration.
Accepted answer
RTC/LDAP for authorization doesn't sound right. RTC does it's own
authorization.
I would have said that RTC (via the JTS) uses LDAP to populate
information in the Jazz "user objects" (such as user name, user ID,
email address, and repository groups it belongs to). I suppose that the
repository groups do have something to do with authorization, but the
primary authorization mechanisms in RTC are via roles and membership in
the Adminstrator list of a project area.
Cheers,
Geoff
On 11/18/2011 1:23 PM, hujirong wrote:
authorization.
I would have said that RTC (via the JTS) uses LDAP to populate
information in the Jazz "user objects" (such as user name, user ID,
email address, and repository groups it belongs to). I suppose that the
repository groups do have something to do with authorization, but the
primary authorization mechanisms in RTC are via roles and membership in
the Adminstrator list of a project area.
Cheers,
Geoff
On 11/18/2011 1:23 PM, hujirong wrote:
lumarwrote:
I have successfully installed and deployed RTC 3.0.1 on WAS.
In addition, I have configured the WAS-LDAP integration (from WAS
admin console), and the RTC-LDAP integration (from the RTC setup
wizard).
The integrations works, as LDAP users are recognized by RTC, and the
nightly synchronization was successful, but there's a point I am still
missing: why is it necessarty to configure this integration twice?
Wouldn't it be enough to WAS-LDAP integration alone?
In fact, I don't understand the need for an additional RTC-LDAP
integration.
I asked the same question before. The answer is: WAS/LDAP is for
authentication and RTC/LDAP is for authorization.
Jirong
2 other answers
I have successfully installed and deployed RTC 3.0.1 on WAS.
In addition, I have configured the WAS-LDAP integration (from WAS admin console), and the RTC-LDAP integration (from the RTC setup wizard).
The integrations works, as LDAP users are recognized by RTC, and the nightly synchronization was successful, but there's a point I am still missing: why is it necessarty to configure this integration twice?
Wouldn't it be enough to WAS-LDAP integration alone?
In fact, I don't understand the need for an additional RTC-LDAP integration.
I asked the same question before. The answer is: WAS/LDAP is for authentication and RTC/LDAP is for authorization.
Jirong