Nintex Gateway for NWC/NAC
Troubleshooting "Tenant Name Does Not Exist" Error in Nintex Gateway
Key Points:
- Prerequisite: Install Nintex Gateway before creating connections.
- URL Accessibility: Ensure required URLs are accessible from the server.
- Proxy Configuration: Verify proxy settings if applicable.
- Tenant Name Verification: Test tenant name with PowerShell.
- AAD SSO Considerations: Allow server access to SSO URLs for federated or SSO-enabled AAD.
Troubleshooting Steps:
- Verify Installation: Confirm Nintex Gateway is installed.
- Check URL Accessibility:
- Contact IT to verify accessibility of:
*.workflowcloud.com- Region-specific
<region>.nintex.io(e.g.,eu.nintex.io) gbo-cli-vib.nintex.iocdn.auth0.comnintex-portal.auth0.com- Region-specific
*.servicebus.windows.net(e.g.,gwyprd01rlyneu01.servicebus.windows.net)
- Contact IT to verify accessibility of:
- Address Proxy Settings: Configure Nintex Gateway for proxy if needed: https://community.nintex.com/automation-cloud-42/nintex-gateway-proxy-configuration-14776
- Test Tenant Name: Run PowerShell on the server:PowerShell
Invoke-WebRequest -Method HEAD -Uri https://tenantname.workflowcloud.com - Allow SSO Access (if applicable): Grant server access to SSO URLs.
Additional Resources:
- Nintex Gateway Installation and Configuration: https://help.nintex.com/en-US/nwc/Content/Gateway/InstallAndConfigure.htm
If issues persist, consult Nintex support for further assistance.
Comments
Post a Comment