This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hi Group, this is what we finally did to resolve the Active Directory
conflict:
The usernames in the AD were all set in lowercase, but the usernames in
Maximo were all set in uppercase, this was causing a conflict. Once the
usernames in Maximo were change to lowercase, as they were in AD, the
conflict was solved.
--
Shirley VĂ©lez-Rivera, Esq.
Legal Advisor
*PM Technology & Consulting Group*
*IBM Business Partner*shirleyvelez.pmtech@gmail.com
info@pmtech-pr.com
(787)525-4363
This is one thing I would have liked be corrected earlier. It shouldn't be a security violation to ignore case for the userid.
You can amend the XML in the cron task to be case neutral - can't recall exact, think maybe (UPPER) before the uid, but google it and you wouldn't then need to worry
Sent from my iPad
> On 24 May 2014, at 14:33, "hendcarw@yahoo.com [MAXIMO]" <MAXIMO@yahoogroups.com> wrote:
>
> This is one thing I would have liked be corrected earlier. It shouldn't be a security violation to ignore case for the userid.
>
>