I'm currently a SysAdmin for a couple of universities, and at one of them, we've been using Carbon Black Cloud for years. I haven't closely followed Broadcom's acquisition of VMware and the nuances surrounding Carbon Black, but I've heard things haven't been smooth. We were recently late on our migration to Azure IDP for Carbon Black Cloud authentication, and the process seemed fairly straightforward based on the guidance provided.
However, after completing the migration, I encountered an issue that left me frustrated. When I tried logging back into Carbon Black, there were no error messages, but the SSO just didn't function. In fact, I had to realize that it's now mandatory to have a registered Broadcom Access account to access Carbon Black. This raises some questions: if SSO is set up, why is it necessary to have a Broadcom account to use it? Has anyone else faced this situation?
4 Answers
I ran into a similar issue! I think the problem is that if the entity ID is set incorrectly, you won’t get past the login screen. I had to double-check the settings and use the STS as they specify—which seems silly. They really should’ve made the documentation clearer. Good luck!
Yeah, it's just Broadcom being their usual self. They really want you to have their accounts in their ecosystem, even if it doesn’t make sense. It's frustrating, I agree. You’d think SSO would simplify things, but clearly not in this situation.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures