Hi Scott,
The feature of storing user attributes in LDAP is not available in
Jetspeed 2.1.x. The only way to store attributes is through user
preferences. However, as you might have noticed, we are currently
working very hard on a complete refactoring of the security framework,
which will become available in Jetspeed 2.2. One of the features of the
new framework will be LDAP synchronization and replication. All security
information related to users, roles, groups, etc. will be stored in a
database, with an option of synchronizing that data with an external
store such as LDAP. By default, an LDAP synchronization and replication
implementation will be provided. This new implementation will make it
possible to define attributes for principal types (user, group, etc),
which can be mapped to LDAP attributes.
The new security implementation will be available in Jetspeed 2.2, which
is due to be released in short notice. The exact release date will be
made public soon, we expect within one month.
regards,
Dennis Dam
Scott Lusebrink wrote:
I have configured jetspeed2 to use ldap using the files from
http://portals.apache.org/jetspeed-2/multiproject/jetspeed-security/ldap.html
http://people.apache.org/~taylor/LDAP/security-spi-ldap.xml
<http://people.apache.org/%7Etaylor/LDAP/security-spi-ldap-atn.xml>
http://people.apache.org/~taylor/LDAP/security-spi-ldap-atn.xml<http://people.apache.org/%7Etaylor/LDAP/security-spi-ldap-atn.xml>
http://people.apache.org/~taylor/LDAP/security-spi-ldap-atz.xml<http://people.apache.org/%7Etaylor/LDAP/security-spi-ldap-atz.xml>
I find that user attributes are still being stored in the database table
PREFS_PROPERTY_VALUE.
Is there anyway to configure jetspeed to store user attributes as part of
the ldap. I'm not above overriding a method in jetspeed if I know where
the update statement is being made. I've traced through into db-ojb-1.0.3
where the actually SQL is being called but I guess I'll need to change it
before this.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
