Newguy 123
asked on
cannot log into OWA or ECP (login loop) after renewing self signed cert 'Microsoft Exchange'.
Hello Experts. In my staging env, i have Exchange 2013CU20 with AD2012R2. I have a strange issue. on my staging exchange servers (3 exhange servers with MB,CAS roles each), the self signed cert 'Microsoft Exchange' had expired. so i renewed it by simply clicking on 'renew' in ECP for that particular certificate for each exchange server. Now, i cannot log into OWA, or ECP. the external OWA and ECP URL are using our third party SSL, but for some reason renewing the self signed cert seems to have broken it. the external and internal URLs are the same with /owa , /ecp respectively. When i try to login, i am redirected back to the log in page, with no error message. I have confirmed that the self signed cert did get updated in IIS backend bindings on each server. What else can i test?
I found this Microsoft article that discusses this: https://blogs.technet.microsoft.com/jasonsla/2015/01/15/the-one-with-the-fba-redirect-loop/
but my issue came when i renewed the self signed certs 'Microsoft Exchange'. Before this, everything was working fine. Please let me know, and thanks in advance.
I found this Microsoft article that discusses this: https://blogs.technet.microsoft.com/jasonsla/2015/01/15/the-one-with-the-fba-redirect-loop/
but my issue came when i renewed the self signed certs 'Microsoft Exchange'. Before this, everything was working fine. Please let me know, and thanks in advance.
I actually just renewed my SSL cert on exchange 2016 and I had the same thing g happen. if I attempt to access the ECP I would keep asking the for password. no error or warning, but the password field would clear again and again. to resolve I just recreated the virtual directories of the ECP. I removed the ECP virtual directory, and re-added it with the same values and reset IIS, and that fixed it for me. I would suggest you try the same.
ASKER
i've just managed to resolve it. I recycled the ECP virtual directory in IIS, and re-assigned the relevant certs to front end site and back end site in IIS, then did IIS reset on each exchange server. that seems to have solved my issue. Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.