WAS with Active Directory - RTC authentication rejected
We have an odd behavior with a WAS 7.0.0.19 hosting RTC 3.0.1.1. We integrated WAS with their Active Directory which we can confirm works by logging into the WAS console and authenticating off their AD.
When we try to log into RTC (in a fresh browser) it rejects the login as a bad username/password. However, if you go into the WAS console and map the specific user to an application role (such as JazzAdmins) the user is able to log in successfully. It's as if the groups are being mapped?
Any suggestions on how to troubleshoot this issue?
When we try to log into RTC (in a fresh browser) it rejects the login as a bad username/password. However, if you go into the WAS console and map the specific user to an application role (such as JazzAdmins) the user is able to log in successfully. It's as if the groups are being mapped?
Any suggestions on how to troubleshoot this issue?
2 answers
Did you do the user and groups mapping when configuring WAS for AD?
We have an odd behavior with a WAS 7.0.0.19 hosting RTC 3.0.1.1. We integrated WAS with their Active Directory which we can confirm works by logging into the WAS console and authenticating off their AD.
When we try to log into RTC (in a fresh browser) it rejects the login as a bad username/password. However, if you go into the WAS console and map the specific user to an application role (such as JazzAdmins) the user is able to log in successfully. It's as if the groups are being mapped?
Any suggestions on how to troubleshoot this issue?