Re: Wasadmin in TEPS
Jared Seaton <[email protected]>
| Newsgroups | gmane.comp.sysutils.tivoli.general |
|---|---|
| Message-ID | <CACoTKfJH-nADypxWwQ3AHxtXxrx4zY9Y_qpHQ48NiyXfq9XoEA__35227.9655672193$1372272842$gmane$org@mail.gmail.com> |
We had the same issue. In the Repository configuration, under "LDAP entity types", and "PersonAccount", we use the following in the search filter to exclude the LDAP wasadmin user. The sAMAccountType=805306368 returns only user records. (&(sAMAccountType=805306368)|(!(cn=wasadmin))) ------ Jared Seaton twitter.com/jmseaton On Wed, Jun 26, 2013 at 10:39 AM, Gregory Mendes <[email protected] > wrote: > Hello All, > > I'm reconfiguring my TEPS to authenticate with LDAP. I was successful > with the WAS configuration and importation of the LDAP certification. > However, my customer has put the wasadmin user in LDAP for Maximo. > > This is effecting the ability to configure my TEPS for LDAP. Has anyone > run into this problem before and if so, is there a way to change the > wasadmin user to something else like wasadmin_itm? > > Regards, > > Gregory R. Mendes > 770-317-8593 > > > _______________________________________________ > TME10 mailing list > [email protected] > Unsubscribe:[email protected] > > _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected]