# AD Provisioning failure **URL:** \ **Category:** IIQ Discussion and Questions\ **Tags:** iqservice, identityiq\ **Created:** [October 7, 2025, 10:45am UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779 "2025-10-07T10:45:33Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![sureshbomm](https://avatars.discourse-cdn.com/v4/letter/s/a4c791/32.png) [@sureshbomm](https://developer.sailpoint.com/discuss/u/sureshbomm)\ **Post date:** [October 7, 2025, 10:45am UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/1 "2025-10-07T10:45:33Z")
Hi Team, We are getting the below error while provisioning to AD. Can you please suggest on this javax.net.ssl.SSLException: Unsupported or unrecognized SSL message at java.base/sun.security.ssl.SSLSocketInputRecord.handleUnknownRecord(SSLSocketInputRecord.java:457) at java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:175) at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111) at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1510) at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1425) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:455) at java.base/sun.security.ssl.SSLSocketImpl.ensureNegotiated(SSLSocketImpl.java:925) at java.base/sun.security.ssl.SSLSocketImpl$AppOutputStream.write(SSLSocketImpl.java:1295) at java.base/sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:234) at java.base/sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:313) at java.base/sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:318) at java.base/sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:160) at java.base/java.io.OutputStreamWriter.flush(OutputStreamWriter.java:248) at java.base/java.io.BufferedWriter.flush(BufferedWriter.java:257) at sailpoint.connector.RPCService.writeContentLengthInfo(RPCService.java:605) at sailpoint.connector.RPCService.writeRequestToOutputStream(RPCService.java:589) at sailpoint.connector.RPCService.execute(RPCService.java:511) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:569) at bsh.Reflect.invokeMethod(Reflect.java:166) at bsh.Reflect.invokeObjectMethod(Reflect.java:99) at bsh.Name.invokeMethod(Name.java:858) at bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:75) at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102) at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47) at bsh.BSHVariableDeclarator.eval(BSHVariableDeclarator.java:86) at bsh.BSHTypedVariableDeclaration.eval(BSHTypedVariableDeclaration.java:84) at bsh.BSHBlock.evalBlock(BSHBlock.java:130) at bsh.BSHBlock.eval(BSHBlock.java:80) at bsh.BSHBlock.eval(BSHBlock.java:46) at bsh.BSHTryStatement.eval(BSHTryStatement.java:88) at bsh.BSHBlock.evalBlock(BSHBlock.java:130) at bsh.BSHBlock.eval(BSHBlock.java:80) at bsh.BshMethod.invokeImpl(BshMethod.java:371) at bsh.BshMethod.invoke(BshMethod.java:267) at bsh.BshMethod.invoke(BshMethod.java:195) at bsh.Name.invokeLocalMethod(Name.java:917) at bsh.Name.invokeMethod(Name.java:804) at bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:75) at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102) at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47) at bsh.BSHBlock.evalBlock(BSHBlock.java:130) at bsh.BSHBlock.eval(BSHBlock.java:80) at bsh.BSHBlock.eval(BSHBlock.java:46) at bsh.BSHIfStatement.eval(BSHIfStatement.java:48) at bsh.BSHBlock.evalBlock(BSHBlock.java:130) at bsh.BSHBlock.eval(BSHBlock.java:80) at bsh.BSHBlock.eval(BSHBlock.java:46) at bsh.BSHIfStatement.eval(BSHIfStatement.java:48) at bsh.BSHBlock.evalBlock(BSHBlock.java:130) at bsh.BSHBlock.eval(BSHBlock.java:80) at bsh.BSHBlock.eval(BSHBlock.java:46) at bsh.BSHIfStatement.eval(BSHIfStatement.java:48) at bsh.BSHBlock.evalBlock(BSHBlock.java:130) at bsh.BSHBlock.eval(BSHBlock.java:80) at bsh.BSHBlock.eval(BSHBlock.java:46) at bsh.BSHIfStatement.eval(BSHIfStatement.java:48) at bsh.Interpreter.eval(Interpreter.java:664) at bsh.Interpreter.eval(Interpreter.java:758) at bsh.Interpreter.eval(Interpreter.java:747) at bsh.util.BeanShellBSFEngine.eval(BeanShellBSFEngine.java:186) at org.apache.bsf.BSFManager$5.run(BSFManager.java:445) at java.base/java.security.AccessController.doPrivileged(AccessController.java:569) at org.apache.bsf.BSFManager.eval(BSFManager.java:442) at sailpoint.server.BSFRuleRunner.eval(BSFRuleRunner.java:249) at sailpoint.server.BSFRuleRunner.runRule(BSFRuleRunner.java:218) at sailpoint.server.InternalContext.runRule(InternalContext.java:1315) at sailpoint.server.InternalContext.runRule(InternalContext.java:1287) at sailpoint.workflow.RapidSetupLibrary.executePostRule(RapidSetupLibrary.java:688) at sailpoint.workflow.RapidSetupLibrary.executePostJoinerRule(RapidSetupLibrary.java:629) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:569) at sailpoint.server.ScriptletEvaluator.doCall(ScriptletEvaluator.java:134) at sailpoint.server.ScriptletEvaluator.evalSource(ScriptletEvaluator.java:63) at sailpoint.api.Workflower.evalSource(Workflower.java:5937) at sailpoint.api.Workflower.advanceStep(Workflower.java:5176) at sailpoint.api.Workflower.advance(Workflower.java:4563) at sailpoint.api.Workflower.startCase(Workflower.java:3149) at sailpoint.api.Workflower.launchInner(Workflower.java:2818) at sailpoint.api.Workflower.launch(Workflower.java:2668) at sailpoint.api.Workflower.launch(Workflower.java:2502) at sailpoint.request.WorkflowRequestExecutor.execute(WorkflowRequestExecutor.java:177) at sailpoint.request.RequestHandler.run(RequestHandler.java:163) Suppressed: java.net.SocketException: Connection reset by peer at java.base/sun.nio.ch.NioSocketImpl.implWrite(NioSocketImpl.java:425) at java.base/sun.nio.ch.NioSocketImpl.write(NioSocketImpl.java:445) at java.base/sun.nio.ch.NioSocketImpl$2.write(NioSocketImpl.java:831) at java.base/java.net.Socket$SocketOutputStream.write(Socket.java:1035) at java.base/sun.security.ssl.SSLSocketOutputRecord.encodeAlert(SSLSocketOutputRecord.java:81) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:419) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:326) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:321) at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:145) … 84 more ---
**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\ **Post date:** [October 7, 2025, 11:22am UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/2 "2025-10-07T11:22:14Z")
Probably you didn’t use the correct port number for HTTPS. Please verify the connection settings. (IQ Service connection settings also) ---
**Author:** ![haideralishaik](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/haideralishaik/32/20414_2.png) [@haideralishaik](https://developer.sailpoint.com/discuss/u/haideralishaik)\ **Post date:** [October 7, 2025, 11:49am UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/3 "2025-10-07T11:49:24Z")
hi @sureshbomm The error `javax.net.ssl.SSLException: Unsupported or unrecognized SSL message` typically indicates a protocol mismatch — likely trying to initiate an SSL/TLS handshake with a non-SSL endpoint. Please verify: - The AD endpoint supports SSL and is using the correct port (e.g., LDAPS on 636). - The connector configuration matches the expected protocol. - The SSL certificate is valid and trusted by the IIQ server. - No proxy or firewall is interfering with the handshake. ---
**Author:** ![sureshbomm](https://avatars.discourse-cdn.com/v4/letter/s/a4c791/32.png) [@sureshbomm](https://developer.sailpoint.com/discuss/u/sureshbomm)\ **Post date:** [October 7, 2025, 12:02pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/4 "2025-10-07T12:02:13Z")
We are disabling the USETLS and saved application, but it came back normally, ![Screenshot 2025-10-07 172832](https://global.discourse-cdn.com/sailpoint/original/3X/1/7/171a610714207820b63c4a55477263d34996dc78.jpeg) ---
**Author:** ![haideralishaik](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/haideralishaik/32/20414_2.png) [@haideralishaik](https://developer.sailpoint.com/discuss/u/haideralishaik)\ **Post date:** [October 7, 2025, 12:13pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/5 "2025-10-07T12:13:06Z")
hi @sureshbomm Could you please give it a try from Debug page and see if the TLS setting persists correctly? ---
**Author:** ![sureshbomm](https://avatars.discourse-cdn.com/v4/letter/s/a4c791/32.png) [@sureshbomm](https://developer.sailpoint.com/discuss/u/sureshbomm)\ **Post date:** [October 7, 2025, 12:42pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/6 "2025-10-07T12:42:44Z")
No luck, I tried same ---
**Author:** ![sagr0812](https://avatars.discourse-cdn.com/v4/letter/s/ac91a4/32.png) [@sagr0812](https://developer.sailpoint.com/discuss/u/sagr0812)\ **Post date:** [October 7, 2025, 1:18pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/7 "2025-10-07T13:18:46Z")
@sureshbomm : From the recent release notes I noticed the recommendation to enable the IQ Service TLS port. I encountered a TLS-related issue some time ago and followed the article linked below. I still needed to take a few additional steps to resolve the TLS problem for IdentityIQ, so I’m sharing those in case they help with your troubleshooting. Thanks > [@TLS Enablement for IQ Service and VAs using Self Signed Certificate](https://developer.sailpoint.com/discuss/t/tls-enablement-for-iq-service-and-vas-using-self-signed-certificate/150820): > > Problem In the latest release of IQService which is released on 1st July,2025, it has become mandatory for all partners which are using SailPoint ISC to provision the data in Active Directory to enable TLS so that AD Connector Rules are triggered as expected. In this article, you will find the high level steps of how to enable TLS for an IQ Service machine using Self Signed Certificate Diagnosis The IQ Service machine which was hosting this component did not had a trusted CA due to which it bec… ---
**Author:** ![RAKRHEEM](https://avatars.discourse-cdn.com/v4/letter/r/f05b48/32.png) [@RAKRHEEM](https://developer.sailpoint.com/discuss/u/RAKRHEEM)\ **Post date:** [October 7, 2025, 2:50pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/8 "2025-10-07T14:50:15Z")
Are you still facing the issue ? ---
**Author:** ![sureshbomm](https://avatars.discourse-cdn.com/v4/letter/s/a4c791/32.png) [@sureshbomm](https://developer.sailpoint.com/discuss/u/sureshbomm)\ **Post date:** [October 7, 2025, 3:04pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/9 "2025-10-07T15:04:26Z")
Yes , please let me know if you have steps to resolve it ---
**Author:** ![phodgdon](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/phodgdon/32/3452_2.png) [@phodgdon](https://developer.sailpoint.com/discuss/u/phodgdon)\ **Post date:** [October 8, 2025, 2:14am UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/10 "2025-10-08T02:14:23Z")
I would uninstall and reinstall the service. I doubt it was installed with the TLS version. Typically you would do a -o 5060 ---
**Author:** ![sureshbomm](https://avatars.discourse-cdn.com/v4/letter/s/a4c791/32.png) [@sureshbomm](https://developer.sailpoint.com/discuss/u/sureshbomm)\ **Post date:** [October 8, 2025, 4:24am UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/11 "2025-10-08T04:24:00Z")
I have installed IQservice on 5050 ![Screenshot 2025-10-08 095111](https://global.discourse-cdn.com/sailpoint/original/3X/0/3/03b2cf685047a6c71370d4f80e02c0e3537b8e68.png) ---
**Author:** ![naveenkumar3](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/naveenkumar3/32/39339_2.png) [@naveenkumar3](https://developer.sailpoint.com/discuss/u/naveenkumar3)\ **Post date:** [October 8, 2025, 4:59am UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/12 "2025-10-08T04:59:37Z")
5050 is not a tls port. If you have installed the iq service on 5050 port. Please uncheck the tls check box from the active directory configuration and also update the port number. Please do a test connection, and see what error you get ---
**Author:** ![sureshbomm](https://avatars.discourse-cdn.com/v4/letter/s/a4c791/32.png) [@sureshbomm](https://developer.sailpoint.com/discuss/u/sureshbomm)\ **Post date:** [October 8, 2025, 5:09am UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/13 "2025-10-08T05:09:49Z")
I tried with unchek IQservices only, but the blow AD configuration empty filed use tls enabled, Unchecked the useTLs and saved it but again those are coming when i open the application ![Screenshot 2025-10-07 172832](https://global.discourse-cdn.com/sailpoint/original/3X/1/7/171a610714207820b63c4a55477263d34996dc78.jpeg) ---
**Author:** ![sureshbomm](https://avatars.discourse-cdn.com/v4/letter/s/a4c791/32.png) [@sureshbomm](https://developer.sailpoint.com/discuss/u/sureshbomm)\ **Post date:** [October 8, 2025, 5:44am UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/14 "2025-10-08T05:44:34Z")
We are getting the below error so can you please let me know how to generate the self-signed certificate and import it, we are using OpenJDK version ![image](https://global.discourse-cdn.com/sailpoint/original/3X/7/4/74c06ca18d038856399c0fba90535c2187d00638.png) ---
**Author:** ![naveenkumar3](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/naveenkumar3/32/39339_2.png) [@naveenkumar3](https://developer.sailpoint.com/discuss/u/naveenkumar3)\ **Post date:** [October 8, 2025, 10:57pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/15 "2025-10-08T22:57:31Z")
Follow the below link for configuring TLS [https://community.sailpoint.com/t5/IdentityIQ-Connectors/IQService-TLS-and-Client-Authentication-Configuration/ta-p/75273](https://community.sailpoint.com/t5/IdentityIQ-Connectors/IQService-TLS-and-Client-Authentication-Configuration/ta-p/75273) ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [December 7, 2025, 10:57pm UTC](https://developer.sailpoint.com/discuss/t/ad-provisioning-failure/184779/16 "2025-12-07T22:57:45Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.