Ask the Community
Groups
Adding Kaseya VSA SAML app fails when using Domain Watch - Connect IT Community | Kaseya
<main> <article class="userContent"> <ol><li>Log into the Passly tenant </li> <li> Select <strong>Single Sign-On Manager.</strong> </li> <li> Select <strong>Kaseya</strong>. </li> <li> Select <strong>Attribute maps</strong>.<br><strong>Attribute Name:</strong> User.domain<br><strong>Outgoing Claim type:</strong> <a href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fschemas.xmlsoap.org%2Fws%2F2005%2F05%2Fidentity%2Fclaims%2Fnameidentifier">http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier</a><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/GZYR91EVL6I4/9-png.png" alt="9.PNG" width="832" height="222" class="embedImage-img importedEmbed-img"></img></li> </ol><p> </p> <p><strong>User Settings</strong></p> <ol><li> Select <strong>Single Sign-On.</strong> </li> <li> Select the<strong> Username.</strong> </li> <li> Select<strong> Add Attribute. <br>Attribute Name: domain<br>Attribute Value: domain.local</strong><strong><br></strong> </li> </ol><p><strong>Note</strong>: This is a case sensitive attribute</p> <p>This should completely resolve to access VSA for your SSO users. </p> </article> </main>