# Active Directory windows 2025 **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [November 8, 2024, 8:11pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408 "2024-11-08T20:11:39Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![USR9000](https://avatars.discourse-cdn.com/v4/letter/u/5f9b8f/32.png) [@USR9000](https://forum.inductiveautomation.com/u/USR9000)\ **Post date:** [November 8, 2024, 8:11pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/1 "2024-11-08T20:11:39Z")
Hello!, I am trying to configure 2025 windows active directory and ignition, on windows 2022 this was a very easy step but now i am getting issues connecting active directory, i am getting the following errors on the logs. Has anyone had success configuring it? java.lang.Exception: Failed connecting to LDAP server. at com.inductiveautomation.ignition.gateway.authentication.impl.LDAPHelper.openContext(LDAPHelper.java:312) at com.inductiveautomation.ignition.gateway.authentication.impl.LDAPHelper.search(LDAPHelper.java:360) at com.inductiveautomation.ignition.gateway.authentication.impl.ActiveDirectoryUserSource.getUsers(ActiveDirectoryUserSource.java:191) at com.inductiveautomation.ignition.gateway.authentication.UserSourceWrapper.doGetUsers(UserSourceWrapper.java:570) at com.inductiveautomation.ignition.gateway.authentication.UserSourceWrapper$UserCacheImpl.doUpdate(UserSourceWrapper.java:297) at com.inductiveautomation.ignition.gateway.authentication.UserSourceWrapper$UserCacheImpl.doUpdate(UserSourceWrapper.java:293) at com.inductiveautomation.ignition.gateway.authentication.AbstractCache$UpdateTask.run(AbstractCache.java:118) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: javax.naming.CommunicationException: simple bind failed: 192.168.8.8:636 at java.naming/com.sun.jndi.ldap.LdapClient.authenticate(Unknown Source) at java.naming/com.sun.jndi.ldap.LdapCtx.connect(Unknown Source) at java.naming/com.sun.jndi.ldap.LdapCtx.(Unknown Source) at java.naming/com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxFromUrl(Unknown Source) at java.naming/com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(Unknown Source) at java.naming/com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(Unknown Source) at java.naming/com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(Unknown Source) at java.naming/com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(Unknown Source) at java.naming/javax.naming.spi.NamingManager.getInitialContext(Unknown Source) at java.naming/javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at java.naming/javax.naming.InitialContext.init(Unknown Source) at java.naming/javax.naming.ldap.InitialLdapContext.(Unknown Source) at com.inductiveautomation.ignition.gateway.authentication.impl.LDAPHelper.openContext(LDAPHelper.java:290) ... 11 common frames omitted Caused by: javax.net.ssl.SSLHandshakeException: No subject alternative names matching IP address 192.168.8.8 found at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source) at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source) at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source) at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source) at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts(Unknown Source) at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.onConsumeCertificate(Unknown Source) at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.consume(Unknown Source) at java.base/sun.security.ssl.SSLHandshake.consume(Unknown Source) at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source) at java.base/sun.security.ssl.TransportContext.dispatch(Unknown Source) at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.ensureNegotiated(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl$AppOutputStream.write(Unknown Source) at java.base/java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.base/java.io.BufferedOutputStream.flush(Unknown Source) at java.naming/com.sun.jndi.ldap.Connection.writeRequest(Unknown Source) at java.naming/com.sun.jndi.ldap.Connection.writeRequest(Unknown Source) at java.naming/com.sun.jndi.ldap.LdapClient.ldapBind(Unknown Source) ... 24 common frames omitted Caused by: java.security.cert.CertificateException: No subject alternative names matching IP address 192.168.8.8 found at java.base/sun.security.util.HostnameChecker.matchIP(Unknown Source) at java.base/sun.security.util.HostnameChecker.match(Unknown Source) at java.base/sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source) at java.base/sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source) at java.base/sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) at java.base/sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source) ... 42 common frames omitted ---
**Author:** ![Benjamin\_Furlani](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/benjamin_furlani/32/66084_2.png) [@Benjamin\_Furlani](https://forum.inductiveautomation.com/u/Benjamin_Furlani)\ **Post date:** [November 8, 2024, 8:25pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/2 "2024-11-08T20:25:40Z")
please add the stack trace to [details="Summary"] This text will be hidden [/details]` section as it will make this much easier to consume see > [@Wiki - how to post code on this forum](https://forum.inductiveautomation.com/t/wiki-how-to-post-code-on-this-forum/77831): > > This thread is intended as a short help file for all those struggling to post formatted code on the forum. Code block formatting Posting formatted code on the forum (and most others) is as simple as selecting the code and pressing the \ button. It works the same as applying Bold or Italic styles to your document. It preserves indentation and applies syntax highlighting. [How to post code] Note that all the \ button does is add three backticks ``` on the line before the code block and anot… ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 8, 2024, 8:27pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/3 "2024-11-08T20:27:31Z")
> [@USR9000](#): > > Caused by: javax.net.ssl.SSLHandshakeException: No subject alternative names matching IP address 192.168.8.8 found This means you're connecting to the AD server via an IP address, that TLS is enabled, and that this IP address is not listed in the certificate being used by the server. ---
**Author:** ![USR9000](https://avatars.discourse-cdn.com/v4/letter/u/5f9b8f/32.png) [@USR9000](https://forum.inductiveautomation.com/u/USR9000)\ **Post date:** [November 8, 2024, 8:28pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/4 "2024-11-08T20:28:08Z")
How do i add it ? is the cert in the Web Server configuration? @Kevin.Herron ---
**Author:** ![USR9000](https://avatars.discourse-cdn.com/v4/letter/u/5f9b8f/32.png) [@USR9000](https://forum.inductiveautomation.com/u/USR9000)\ **Post date:** [November 8, 2024, 8:30pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/5 "2024-11-08T20:30:54Z")
I guess is this something on ignition configuration or domain controller? I am a abit confused. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 8, 2024, 8:32pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/6 "2024-11-08T20:32:58Z")
The only configuration on the Ignition side is the hostname/IP you use to connect. You might need to connect via a hostname instead, or get ahold of that certificate (might need help from your IT) to see what hostnames and IPs are listed in it. ---
**Author:** ![USR9000](https://avatars.discourse-cdn.com/v4/letter/u/5f9b8f/32.png) [@USR9000](https://forum.inductiveautomation.com/u/USR9000)\ **Post date:** [November 8, 2024, 8:40pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/7 "2024-11-08T20:40:27Z")
According to my IT admin, the ip is included in the cert, i will try to connect using the hostname to see if i see any differences ---
**Author:** ![USR9000](https://avatars.discourse-cdn.com/v4/letter/u/5f9b8f/32.png) [@USR9000](https://forum.inductiveautomation.com/u/USR9000)\ **Post date:** [November 8, 2024, 8:50pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/8 "2024-11-08T20:50:08Z")
Same issue using the hostname, the hostname resolves on the windows server that ignition is running on, any other suggestions ? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 8, 2024, 8:51pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/9 "2024-11-08T20:51:00Z")
Same error but instead of the IP the error says the hostname isn't found? ---
**Author:** ![USR9000](https://avatars.discourse-cdn.com/v4/letter/u/5f9b8f/32.png) [@USR9000](https://forum.inductiveautomation.com/u/USR9000)\ **Post date:** [November 8, 2024, 8:54pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/10 "2024-11-08T20:54:37Z")
correct, and when i ping the hostname on the command prompt, the machine is able to resolv the hostname. So i am unsure why the Active directory is complaining . ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 8, 2024, 8:57pm UTC](https://forum.inductiveautomation.com/t/active-directory-windows-2025/98408/11 "2024-11-08T20:57:31Z")
AD isn't complaining; you are being presented with a certificate that does not contain the hostname or IP address. Either something on your network is interfering and presenting Ignition with a different certificate, or your IT admin is wrong and the certificate doesn't have these items in it. You can edit `ignition.conf` and add an entry to the "additional parameters" section like this: ```python wrapper.java.additional.X=-Djavax.net.debug=ssl:handshake:verbose ``` where `X` is the next number in the sequence. Restart Ignition, then let it try to connect, and the wrapper.log files will contain a bunch of verbose logging output about the connection attempt. You probably need to work with support at this point because sharing that log on the forum might not be a good idea.