Being able to connect to more than one active directory for single sign on would be an amazing feature. I have a setup where I have multiple active directory forests and MUST keep them separate and disconnected. I use multiple orgs and am enjoying it, but without being able to join to each active directory with single sign on, I am afraid user adoption of the portal will be minimal and not worth the effort. Please add this as soon as possible.85 votes
Build some nice and easy SSO integration for Azure AD similar to salesforce. Would be very nice to be able to do this like you can with salesforce etc, I'm very surprised that in the re-design for SSO that it wasnt brought in.58 votes
When users login using SSO they get the default organization. They do not have a way to change to another organization. A fast organization change like the admins have would correct this issue.32 votes
We need to able to track last user login into the KACE appliances, if the user has not logged in last 30 days, it would be disabled. We need this for PCI compliance to avoid fines.16 votes
The user account that is created when enabling SSO has a forward slash in the User Principal Name (UPN).
Azure does not like the forward slash and this causes a 'Data Validation Error'.
I'd like to request a change to the format of the user logon name that is created by the Kace SMA when it joins to the domain.12 votes
About half of our workforce is off-site, many of them on Chromebooks where there is no Kerberos authentication. Please add a feature where Kerberos SSO can be enabled on a per-IP range basis so that we can enable SSO for on-prem users only. If Kerberos is enabled for computers that aren't using Kerberos, they see two login prompts and have to login twice.
Enable Kerberos: Yes
Limit Kerberos to IP Range(s): 10.10.5.0/22
This would allow us to use Kerberos for on-prem end-users but prevent the double login prompt for appearing for off-site VPN users (about half of our workforce).3 votes
- Don't see your idea?