/build/static/layout/Breadcrumb_cap_w.png

No SSO after K1000 migration

I migrated our K1000 to a VK1000 this morning. Everything looks good except single sign on no longer works. We're in AD, and LDAP is working fine for my AD users. I'm guessing that there may be an issue with the kbox-HTTP user object, but I'm not sure what to check. Any ideas?

Thanks.

2 Comments   [ + ] Show comments
  • Did you unjoin the K1000 and then go and add the VK1000 back to the domain via Settings> Control Panel > Security Settings?

    You may need to delete or disable the KBOX accounts created for user and computer in AD. - nshah 8 years ago
    • Thanks. I did that (had to be given permissions first to default Computers OU), but it still isn't working. I have a ticket open with Dell, but if you know of anything I can check (like SPN or UPN for the objects), that would be great. Tx. - tpr 8 years ago
  • What DNS are you using for the K1000 in the network settings. If we use our internal DNS, then SSO works, but we have to use Google DNS in order to connect to the Office 365 exchange server for mail imports... which in turn breaks SSO. - AndyH 8 years ago
    • We're using our domain dns, same as we were with the old K1000. - tpr 8 years ago

Answers (1)

Posted by: tpr 8 years ago
2nd Degree Black Belt
0
4 months later, I have fixed the SSO problem by going into the Network Settings and unchecking the "Autogenerate Server Name", then rebooting. I never noticed that before, and I have zero idea why it would be checked by default.


Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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