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:

  1. Verify Installation: Confirm Nintex Gateway is installed.
  2. 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.io
      • cdn.auth0.com
      • nintex-portal.auth0.com
      • Region-specific *.servicebus.windows.net (e.g., gwyprd01rlyneu01.servicebus.windows.net)
  3. Address Proxy Settings: Configure Nintex Gateway for proxy if needed: https://community.nintex.com/automation-cloud-42/nintex-gateway-proxy-configuration-14776
  4. Test Tenant Name: Run PowerShell on the server:
    PowerShell
    Invoke-WebRequest -Method HEAD -Uri https://tenantname.workflowcloud.com
    
  5. Allow SSO Access (if applicable): Grant server access to SSO URLs.

Additional Resources:

If issues persist, consult Nintex support for further assistance.

Comments

Popular posts from this blog

Blocking Error during K2 5.6 Server migration

Client Credentials flow with K2 Cloud with Odata, Workflow REST or SCIM

Blocking error RegisterServiceInstanceObjects when upgrading to K2 5.6/5.7