ConnectorAfterCreate Rule No Longer Running Since 7/1

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Is anyone else having issues with ConnectorAfterCreate rules lately?

Our ConnectorAfterCreate Rule is no longer running since 7/1.
This rule isn’t something new. This was part of our original implementation. It’s configured for our main AD source. I can see on 7/1 we received a new automatic upgrade via update service. After that, the log file (first line of the rule) isn’t appending new data. I rebooted the windows services, I rebooted the windows server, I rebooted the Linux VA servers. None of these have solved the issue.

I read suggestions here and created a new debug ConnectorAfterCreate rule which should create a new log to show if the rule is running. And it didn’t create the log… so I’m stumped. Seems like it’s not running at the most basic level, even though it worked fine 7/1.

I opened a support ticket too (just 7 hours ago), but no reply yet.

2

have you deleted non-TLS port entry from IQ service registry? if not delete it

1 Like
3

You are so fast!
Sailpoint should be paying you, if you’re not working for them already.

If anyone else has this issue, here are is the guide:

Just scroll down to " Disabling Non-TLS Communication for an Existing IQService Instance" and make sure to stop and start the iqservices after.

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.