For large IT operations with many locations, relying on uniform use of the Noah User Administration as it is designed today is difficult to enforce. For example, there are still locations where all hearing care professionals use the default ABC login to access Noah.
By using the Windows Domain user accounts that are already established, controlled, and in use for other systems, IT operations can easily implement a more secure and uniform data security.
Windows Directory Service integration will ensure that the Noah users are indeed using individual identities when working with Noah System. The user will be required to authenticate their access to Noah by the same credentials they use to log into their Windows computers in the corporate domain.
PLEASE NOTE: HIMSA tests Active Directory in a single-domain environment. We do not test configurations involving multiple domains or subdomains. While customers may be able to get this working in their environment, we do not provide support for multi-domain or subdomain setups.
IMPORTANT ISSUE:
HIMSA has become aware of an issue with Noah version 4.117.0 when setting up Active Directory integration for Noah System. In this instance, Active Directory integration will only work when using the default suggested group names. Custom group names will not work. The default suggested group names are:
- NoahAdministrators
- NoahLevel1Users
- NoahLevel2Users
HIMSA is investigating a solution.
__________________________________________________________
HIMSA