/build/static/layout/Breadcrumb_cap_w.png

SAML problem with SMA

We were using ldap successfully but have a need to use SAML SSO.  We followed the documentation to get connected and ran into a problem.  In LDAP the login ID is first initial last name from Active Directory; but in azure what is sent as a claim is the email address.  So we end up with a new account for each user.  Futhermore required fields like job title and division are not being sent at all.  Was working with someone from KACE but he was not able to get the problem resolved.


He did have me install a chrome SAML utility which shows the same XML. so for username from Azure what it sends is "<Attribute Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name">"


Has anyone had any luck declaring additional "claims" in azure?  This far we cant seem to get Azure to send what we need. 


2 Comments   [ + ] Show comments
  • Anyone? Bueller? - barchetta 1 year ago
  • Did you ever get this working? - bseaton 5 months ago

Answers (3)

Posted by: cyclolink 2 months ago
White Belt
0

The secret is in how you set it up.  The documentation that Quest provides is pretty good but the issue is they use App Registration rather than an Enterprise App.  If you create an Enterprise App it also creates an app under App Registration.  Navigate to the app under App Registration and follow the same instructions.  The only changes that you will need to make are:

  1. Enter the entity ID within the Single Sign-On info within the Enterprise application
  2. Add any additional claims in the claims section of Single Sign-On
  3. Do a test connection using Azure SSO test and capture it with the SAML Message Decoder Chrome extension.  Grab the certificate from the SAML message and update it in Kace.
Posted by: barchetta 4 months ago
Orange Belt
0

What we ended up doing is using the email address as the primary key in the saml setup.  It can also be done by setting up claims so that for the UID you map the email address.  lots of ways to go about this.  However, if you are using Azure App registration you are limited as to what claims can be used.  There is a way to use enterprise registration where you can bring in more claims but I digress.

If you want to use the email address this is how we map to the claim under email and it is set as the primary key. 

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress

We were also using the UNC at one point and if you are azure it should be the email address.. we were using

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

Hope this helps... that chrome extension is KEY in troubleshooting.. there seem to be only a few people on kace support that truly understand this and I wish I could remember a name but I cannot.

One thing though, if you have multiple email addresses you have to be careful here that ldap doesnt change the email address.  Using ldap in conjunction with saml can be tricky depending on your configuration so keep this in mind.

Posted by: barchetta 4 months ago
Orange Belt
0

Well this is funny. I just answered my own question.. oh well, I hope it helps someone. :)

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ