Tyler Identity Azure Setup

Owned by Knowledge Assistant
Last updated: Dec 09, 2024 by Moriah Yorkey
1 min read
Description of Issue

Client would like to transition to using Azure AD to accommodate multiple domains.

Context

  • Tyler Identity (TID)

  • Azure authentication

  • Munis 2019.x, 2020.x

  • Tyler Deploy

  • SQL Queries

Cause

Clients that use Tyler ID require ADFS or Azure to authenticate multiple domains will need to update their Authentication Type in Tyler Deploy (If they have access to Product Configurations).

Resolution

Azure AD

  1. Log into Tyler Deploy

  2. Navigate to Product Configuration | Tyler Identity

  3. Change Local Authentication Type to Azure AD

  4. Enter the Azure FQDN in the following format fs.city.local (do not include HTTPS or slashes)

  5. Enter Azure WTRealm in the following format urn:TylerIdentityTest 

  6. Verify the Azure Metadata Address looks correct. Example: https://fs.city.local/federationmetadata/2007-06/federationmetadata.xml

  7. Redeploy Tyler ID

  8. Run the following query against the tylerid{env} database
    SQL: Deletes all users from the TID database except the built in tyleradmin 

    • DELETE FROM MembershipReboot.UserAccounts WHERE not Username='tyleridentityadmin@tylertech.com'

  9. Update the integrated products HUB, MUNIS, etc... "UserNameClaim": "winaccountname"

Additional Information

Contact Tyler Systems Management Support or submit a case via the Online Support Client Portal for additional assistance.

Â