Changeset 471
- Timestamp:
- 12/20/07 15:49:38 (8 months ago)
- Location:
- trunk/etc
- Files:
-
- 2 modified
-
c2s.xml.dist.in (modified) (3 diffs)
-
sm.xml.dist.in (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/etc/c2s.xml.dist.in
r465 r471 431 431 <type>ad</type> 432 432 --> 433 433 434 <!-- LDAP attribute that holds the user ID (default: uid) --> 435 <uidattr>uid</uidattr> 436 <objectclass>posixAccount</objectclass> 437 <pwattr>userPassword</pwattr> 438 <!-- if you use included jabberd.schema use this: 434 439 <uidattr>jid</uidattr> 440 <objectclass>jabberUser</objectclass> 441 <pwattr>jabberPassword</pwattr> 442 --> 443 435 444 <!-- Attribute that holds jabber account status. Must be TRUE for AD, 436 445 and 1 for other LDAP server. … … 440 449 --> 441 450 <fulluid/> 442 <pwattr>jabberPassword</pwattr>443 451 <!-- If pwscheme is not defined, then passwords are stored in clear 444 452 text and digest authentication may be done. … … 447 455 For now, sha, ssha and plain may be specified --> 448 456 <!-- <pwscheme>ssha</pwscheme> --> 449 <objectclass>jabberUser</objectclass>450 457 451 458 <!-- base DN of the tree. You should specify a DN for each -
trunk/etc/sm.xml.dist.in
r470 r471 207 207 208 208 <!-- LDAP attribute that holds the user ID (default: uid) --> 209 <uidattr>uid</uidattr> 210 <objectclass>posixAccount</objectclass> 211 <pwattr>userPassword</pwattr> 212 <!-- if you use included jabberd.schema use this: 209 213 <uidattr>jid</uidattr> 210 211 214 <objectclass>jabberUser</objectclass> 215 <pwattr>jabberPassword</pwattr> 216 --> 212 217 213 218 <!-- see authreg.ldapfull int c2s.xml for description. -->