We have Remedy 7.0.1 running on Win2003 servers. I recently configured our test server's AREA LDAP plug-in to authenticate users against our Active Directory server. I've setup the AR server to authenticate unregistered users and cross reference blank passwords. Users that exist in the user form without a password are authenticated against AD without a problem.

The problem I have is that if a user sets a password in Remedy, they can use that password and do not authenticate against AD. The problem with that is that Remedy does not enforce password aging and strong passwords. Is there any way to force authentication against AD and dis-allow authentication against the user form?

Can I do a mass-update on the user form and set user password to blank and then somehow lock them out from setting passwords in Remedy?

Thanks!

Yes, if your users don't have any permission on the password field, they can't change their password.

If you upgrade to AR System 7.1, you can have password policy enforcement.

Ahhhh... Permissions. Of course. I feel a bit sheepish about now...

As soon as I get a few more things caught up, I plan on diving into the 7.1 upgrade.

Thanks for your help!

Hello Wags,

I am developing a project plan for the integration of Remedy and Active Directory. Can you help me with the steps/activities/work breakdown for the project.

I am actually running 6.3 now but might upgrade to 7.1 soon. My upgrade depends on how well i can integrate Remedy and AD on either version.

Thanks, i really need this.