<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>SAML on Matt Allford</title><link>https://www.mattallford.com/tags/saml/</link><description>Recent content in SAML on Matt Allford</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 28 Mar 2016 11:56:37 +0000</lastBuildDate><atom:link href="https://www.mattallford.com/tags/saml/index.xml" rel="self" type="application/rss+xml"/><item><title>vSphere New PSC Deployment - Could Not Parse SAML Token For Authentication</title><link>https://www.mattallford.com/vsphere-new-psc-deployment-could-not-parse-saml-token-for-authentication/</link><pubDate>Mon, 28 Mar 2016 11:56:37 +0000</pubDate><guid>https://www.mattallford.com/vsphere-new-psc-deployment-could-not-parse-saml-token-for-authentication/</guid><description>&lt;p&gt;In my lab, I deployed vCenter using the appliance as an embedded node using vCenter 6.0.0b. I purposely deployed this build, as an embedded deployment for two reasons:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;I haven&amp;rsquo;t used the appliance before, and I wanted the lab to be simple, but I also wanted to see the upgrade process in action on the appliance&lt;/li&gt;
&lt;li&gt;I wanted to deploy an external PSC and follow the process to re point the original VC server to the new external PSC, as outlined here: http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID-E7DFB362-1875-4BCF-AB84-4F21408F87A6.html&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;My lab is deployed in a nested environment sitting on top of VMWare Workstation. So I deployed a new node to the environment which was an external PSC, joined to the original SSO domain and site.&lt;/p&gt;</description></item></channel></rss>