# UI Bug: Home Realm Discovery does not show tenant domain if applied via Terraform

**URL:** <https://community.auth0.com/t/ui-bug-home-realm-discovery-does-not-show-tenant-domain-if-applied-via-terraform/190247>\
**Category:** Get Help\
**Tags:** connections, saml-enterprise-connection\
**Created:** [August 6, 2025, 2:34pm UTC](https://community.auth0.com/t/ui-bug-home-realm-discovery-does-not-show-tenant-domain-if-applied-via-terraform/190247 "2025-08-06T14:34:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![billy2](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@billy2](https://community.auth0.com/u/billy2)\
**Post date:** [August 6, 2025, 2:34pm UTC](https://community.auth0.com/t/ui-bug-home-realm-discovery-does-not-show-tenant-domain-if-applied-via-terraform/190247/1 "2025-08-06T14:34:21Z")

</div>

I’ve been using terraform to create SAML connections; however, I realized that when I apply the [tenant\_domain](https://registry.terraform.io/providers/auth0/auth0/latest/docs/resources/connection#saml-connection) property , it does not appear in the UI. I inspected the network calls and can see it in the response and it also does route to the connection properly. Seems like a simple UI Bug where it just isn’t populating but it is definitely confusing from a user standpoint.

 ![Screenshot 2025-08-06 at 10.24.35 AM](https://global.discourse-cdn.com/auth0/original/3X/e/9/e9f7ec553d25d834717d1613f40f7b03424169e1.png)

---

<div class="post-metadata">

**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\
**Post date:** [August 6, 2025, 4:38pm UTC](https://community.auth0.com/t/ui-bug-home-realm-discovery-does-not-show-tenant-domain-if-applied-via-terraform/190247/3 "2025-08-06T16:38:02Z")

</div>

Hi @billy2

Thank you for reaching out to us!

After reading through your use-case, I did some digging around and it appears that “tenant\_domain” is merged with the “domain\_aliases” array, and the resultant array is what is used for Home Realm Discovery. " tenant\_domain " seems to be more of a legacy field that only accepts a String and is limited to one entry.

Doing some testing with the [Management API](https://auth0.com/docs/api/management/v2/connections/get-connections-by-id), “tenant\_domain” is not automatically created when setting “domain\_aliases”. As you have mentioned, using only `tenant_domain` seems to be working correctly, but it will indeed not list the configured “tenant\_domain” in the connection’s “Identity Provider Domains” box.

My recommendation is to just use the “[domain\_aliases](https://registry.terraform.io/providers/auth0/auth0/latest/docs/resources/connection#domain_aliases-1)” array to record your customer’s email domains that should be routed to the connection in question, and the “tenant\_domain” attribute can be omitted from the configuration. As the connection is working correctly for you, this is solely a UI issue ( which can create confusion).

This was similarly mentioned in the following [Community Post](https://community.auth0.com/t/how-to-add-identity-provider-domains-in-saml-connection-using-terraform/109783) as well, where `domain_aliases` was used in the same fashion instead of `tenant_domain`.

I would also recommend to provide this feedback to our Product team via the [Feedback](https://auth0.com/feedback) page. Others can vote on the suggestion and this can lead to UI improvements and fixed to avoid such confusions in the future.

Hope this helped!  
Gerald

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [August 20, 2025, 4:38pm UTC](https://community.auth0.com/t/ui-bug-home-realm-discovery-does-not-show-tenant-domain-if-applied-via-terraform/190247/4 "2025-08-20T16:38:49Z")

</div>

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