ScriptExecutor service disabled due to non-TLS port configured for IQService

Hello Everyone,

Seen this error before?

Also, there is a TLS port (5053) and non-TLS port (5050) configured for IQService and it was never a problem before while executing native scripts.

But, everything works well when the native script is detached from the AD source settings and not sure what causes the ScriptExecutor service stopped. When I checked the services at the time I got the error, I see the service was up and running.

Any ideas to resolve this issue?

1 Like

You must remove non-TLS port (5050) from the configuration.

Thank you.

I disabled the non-TLS port (updated the port number from 5050 to 0) in IQService and the scripts are now called.

Why is necessary to be removed? And I see the IQService was updated recently, is the latest version enforced to be communicated only with TLS port, else services are temporarily stopped?

2 Likes

Hi,
Yes, recently SailPoint published newsletter to disable all before and after scripts executions if non-tls port is enabled.

2 Likes