# Non-Employee Risk Management SaaS connector

**URL:** <https://developer.sailpoint.com/discuss/t/non-employee-risk-management-saas-connector/54142>\
**Category:** Bugs\
**Tags:** non-employees, sailpoint-identity-security\
**Created:** [April 25, 2024, 11:27am UTC](https://developer.sailpoint.com/discuss/t/non-employee-risk-management-saas-connector/54142 "2024-04-25T11:27:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\
**Post date:** [April 25, 2024, 11:27am UTC](https://developer.sailpoint.com/discuss/t/non-employee-risk-management-saas-connector/54142/1 "2024-04-25T11:27:54Z")

</div>

# What problem are you observing?

Currently, we’re connecting our ISC development tenant with our NERM development tenant, using the new Non-Employee Risk Management connector. We have setup the connector as documented, but fails on a test connection with the error:

> Error: seczetta.eu is not a valid domain.

Clearly, there is some (incorrect) filtering / checking going on in the connector itself, since this was the PoC / development environment provided to us by SailPoint.

# What is the correct behavior?

There should be not ‘filter’ or check on domain name, same as for the WebServices connector

# What product feature is this related to?

ISC and NERM

# What are the steps to reproduce the issue?

Setup a new NERM connector to a tenant with seczetta.eu in the domain name.

# Do you have any other information about your environment that may help?

N/A