<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Identity-Broker on Clouds and Unicorns</title><link>https://cloudsandunicorns.com/tags/identity-broker/</link><description>Recent content in Identity-Broker on Clouds and Unicorns</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2007–2026, Scott Bowe</copyright><lastBuildDate>Mon, 06 Jul 2026 23:28:47 -0500</lastBuildDate><atom:link href="https://cloudsandunicorns.com/tags/identity-broker/index.xml" rel="self" type="application/rss+xml"/><item><title>How to use VCF Operations and VCF SSO behind a load balancer</title><link>https://cloudsandunicorns.com/2026/07/how-to-use-vcf-operations-and-vcf-sso-behind-a-load-balancer/</link><pubDate>Mon, 06 Jul 2026 23:28:47 -0500</pubDate><guid>https://cloudsandunicorns.com/2026/07/how-to-use-vcf-operations-and-vcf-sso-behind-a-load-balancer/</guid><description>
&lt;p&gt;I dropped the operations node out of my VCF lab cluster last week and replaced it with two new ones. Nothing dramatic, just routine lab upkeep, the kind of thing I've done more times than I can count over fifteen or twenty years of running this stack. Then I went to log in through the FQDN like I always do, and SSO just refused to work.&lt;/p&gt;
&lt;p&gt;Not a slow login, not a weird certificate warning. A flat rejection, straight from the identity broker, telling me my redirect URL was invalid.&lt;/p&gt;</description></item></channel></rss>