running through the big 5.5 upgrade this weekend and I'm running into a currious issue.After installing a fresh copy of prism central 5.5 (we never used it befoer 5.5, but now it's required), I cannot seem to get the ad authentication to work. The connection is configured, and I can still search for and map groups to roles (so I know at least some ofthe AD integration is working), but when it comes time to actually login ... I keep get that I'm using a bad username/password. Release notes mention that everything is UPN based, but that's basically always been the case for my company anyway (we've always logged in using upn).Anyone else run into this?
Best answer by Justin-DynamicD
Update: it seems this UPN restriction extends ot the service acocunts as well: I had ot update the service account to be a complete upn then things apparently kicked in.