Cisco Bug: CSCvt06058 - MRA SSO x12.5 guide. ADFS command is confusing and not clearly explained.
Apr 24, 2020
- Cisco TelePresence Video Communication Server (VCS)
- Cisco TelePresence Video Communication Server Model
- Cisco Expressway
Known Affected Releases
X12.5 X12.5.1 X12.5.2 X12.5.3 X12.5.4 X12.5.5 X12.5.6 X12.5.7
Symptom: This is a part of guide https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X12-5/exwy_b_mra-expressway-deployment-guide/exwy_b_mra-expressway-deployment-guide_chapter_01000.html#reference_A26C25F0BB9019656A84E8208AFBE864: 1. In Windows PowerShell®, repeat the following command for each Expressway-E's <EntityName>: Set-ADFSRelyingPartyTrust -TargetName "<EntityName>" -SAMLResponseSignature MessageAndAssertion It's not clear what EntityName is. This confused customers and force them to use FQDN of EXP-E for EntityName, which is incorrect. EntityName - must be a "Display name" as it set in ADFS for expressway's Relating Party Trust. 2. "Repeat the following command for each Expressway-E" also confusing part, as exprted metata data contains all information about all expressway in cluster, you have to run the command one time, once per Relying Party Trust created on ADFS. Conditions: Installation/configuration of MRA SSO using guide https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X12-5/exwy_b_mra-expressway-deployment-guide/exwy_b_mra-expressway-deployment-guide_chapter_01000.html
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases