From portal-commits at lists.jboss.org Sat Mar 3 18:14:55 2007 Content-Type: multipart/mixed; boundary="===============8106154528060996339==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r6515 - docs/trunk/referenceGuide/en/modules. Date: Sat, 03 Mar 2007 18:14:55 -0500 Message-ID: --===============8106154528060996339== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: bdaw Date: 2007-03-03 18:14:55 -0500 (Sat, 03 Mar 2007) New Revision: 6515 Modified: docs/trunk/referenceGuide/en/modules/identity.xml docs/trunk/referenceGuide/en/modules/ldap.xml Log: update Modified: docs/trunk/referenceGuide/en/modules/identity.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- docs/trunk/referenceGuide/en/modules/identity.xml 2007-03-03 22:33:19 U= TC (rev 6514) +++ docs/trunk/referenceGuide/en/modules/identity.xml 2007-03-03 23:14:55 U= TC (rev 6515) @@ -815,7 +815,7 @@ Delegating UserProfile module - Delegating UserProfile module implementation has very speci= fic role. When we use storage mechanism like LDAP we may not be able to map= all + Delegating UserProfileModule implementation has very specif= ic role. When we use storage mechanism like LDAP we may not be able to map = all user properties into LDAP attributes because of schema limitation= s. To solve this problem we use database to store such not mapped propertie= s. Delegating user profile module will recognize if property is mapp= ed as ldap or da= tabase end delegate setProperty()/getProperty() met= hod invocation to proper module implementation. This is implemented in @@ -868,7 +868,7 @@ Database UserProfile module implementation - Because of behaviour described in previous section database= UserProfile module needs some special capabilities. If user is present in + Because of behaviour described in previous section database= UserProfileModule needs some special capabilities. If user is present in LDAP server but property we want to store isn't mapped as LDAP at= tribute such property need to be stored in database. But to store the property user need to be synchronized from ldap into database= first Class org.jboss.portal.identity.db.HibernateUserP= rofileModuleImpl has additional synchronization features. @@ -876,25 +876,26 @@ synchronizeNonExistingUsers - when set to "true" if user on which we want to perform operation does= n't exist it will - create it in database + create it in database. Default is "true". acceptOtherImplementations - if set to "true" module will accept user objects other than org.jboss.portal.identity.db.HibernateUserImpl. This is needed to enable cooperation with UserModule implementati= ons other - than org.jboss.portal.identity.db.HibernateUserMo= duleImpl + than org.jboss.portal.identity.db.HibernateUserMo= duleImpl. Default is "true". - defaultSynchronizePassword - if this option is set the value will be used as password for synchroni= zed user. + defaultSynchronizePassword - if this option is set, the value will be used as a password for synchr= onized user. randomSynchronizePassword - if this option is set to "true" synchronized user will have random gene= rated password. - This is mostly for the security reasons. + This is mostly used for the security reasons. Default is "f= alse". sessionFactoryJNDIName -= JNDI name under which this user will be registered. - profileConfigFile - file= with user profile configuration + profileConfigFile - file= with user profile configuration. If this option is not set, and we use del= egating UserProfileModule, = + profile configuration will be obtained from it. Modified: docs/trunk/referenceGuide/en/modules/ldap.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- docs/trunk/referenceGuide/en/modules/ldap.xml 2007-03-03 22:33:19 UTC (= rev 6514) +++ docs/trunk/referenceGuide/en/modules/ldap.xml 2007-03-03 23:14:55 UTC (= rev 6515) @@ -152,10 +152,122 @@ LDAP Identity Modules TODO: + + UserModule + + LDAPUserModuleImpl + TODO: + org.jboss.portal.identity.ldap.LDAPUserModuleImpl option= s: + + + - = + + + - + + + + + + LDAPExtUserModuleImpl + TODO: + org.jboss.portal.identity.ldap.LDAPExtUserModuleImpl opt= ions: + + + - + + + - + + + + + + + RoleModule + + LDAPRoleModuleImpl + TODO: + org.jboss.portal.identity.ldap.LDAPRoleModuleImpl option= s: + + + - + + + - + + + + + + LDAPExtRoleModuleImpl + TODO: + org.jboss.portal.identity.ldap.LDAPExtRoleModuleImpl opt= ions: + + + - + + + - + + + + + + + MembershipModule + + LDAPStaticRoleMembershipModuleImpl + TODO: + org.jboss.portal.identity.ldap.LDAPStaticRoleMembershipM= oduleImpl options: + + + - + + + - + + + + + + LDAPStaticGroupMembershipModuleImpl + TODO: + org.jboss.portal.identity.ldap.LDAPStaticGroupMembership= ModuleImpl options: + + + - + + + - + + + + + + + UserProfileModule + + LDAPUserProfileModuleImpl + TODO: + org.jboss.portal.identity.ldap.LDAPUserModuleImpl option= s: + + + - + + + - + + + + + - Place holder 3 + LDAP server tree shapes + + + Supported LDAP servers TODO: - --===============8106154528060996339==--