Reset Search



KB43621 - Pulse One On-premises Enterprise SSO/SAML breaks after upgrade to 2.0.1743

« Go Back


Last Modified Date2/1/2018 8:15 PM
This article describes an issue with Pulse One On-premise where SAML authentication stops working upon upgrading the Pulse One appliance to 2.0.1743


Problem or Goal
After upgrading Pulse One On-Premise appliance to version 2.0.1743, Enterprise SSO/SAML authentication fails with the following error displayed in Pulse One authentication response:  
Error in SAML processing : 'No SP configured with entity ID'
This issue occurs due to a change in the way the entity ID of the Pulse One device was used in previous releases vs. Pulse 2.0.1743.

In the previous versions of Pulse One, the entity Id of the Pulse One set in the metadata file that got imported to the PCS device was:

which generated the entity ID as:


After upgrading to Pulse One 2.0.1743, the entity ID gets set by extracting the common name from its device certificate, resulting in the entity ID getting modified to:


This causes SAML authentication to fail because there is no SP configured on the PCS device with this entity ID.  
Follow the steps below to resolve this issue by modifying the metadata file on the PCS device for the Pulse One IdP configuration and reload it with the correct entity IDs:
  1. On the PCS device, sign in as admin and go to System > Configuration > SAML.
  2. Select the Metadata entry for the Pulse One Service Provider.
User-added image
  1. Click on the Download icon indicated in the screenshot above.  
  2. Open the downloaded metadata file with a text editor.  It will look similar to the example below:
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" entityID="">
<md:SPSSODescriptor WantAssertionsSigned="0" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
<md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="" index="1" isDefault="1"/>
  1. Modify the URL in the entityID and the Location fields from to where is the common name found in the Pulse One device certificate.  
  2. Save the file with a new name. 
  3. Navigate to System > Configuration > SAML and click New Metadata Provider.
  4. Enter a name for the Metadata provider then select Local and click Choose File.
  5. Browse for and select the Metadata file that was modified in step 5.
  6. Select Accept Unsigned Metadata.
  7. At the bottom of the page, select Service Provider for this Metadata provider.  
  8. Save Changes.
  9. Go to Signing In > Sign-In SAML > Identity Provider and scroll to the bottom of the page where the Peer Service Providers are listed.
  10. Select the original Peer Service Provider and click Delete SP.
  11. Navigate to System > Configuration > SAML and delete the Metadata entry that was used before. 
  12. Navigate to Signing In > Sign-In SAML > Identity Provider and scroll to the bottom of the page and click Add SP.
  13. From the the Entity ID drop-down menu, select the Entity ID of the SP that was modified in step 5 above.  (Configure any other custom settings here that are needed.)
  14. Click Save Changes.
  15. Navigate to Authentication > Signing In > Metadata Provider.
  16. Download the Metadata provider then open the contents in a text editor.
  17. Copy the contents of the metadata provider.
  18. Login to Pulse One as local admin.
  19. Select the settings gear in the upper right corner of the page.and select Pulse One Properties.
  20. Expand the Enterprise Connections section.
  21. Click the edit icon for the SAML Identity Provider Metadata file.  This will open a text view of the metadata contents.
  22. Paste the contents of the metadata file copied in step 21 and click Save.  This will update the SAML Service Provider Metadata contents as required.
  23. Sign out of Pulse One and log back in with SSO Enterprise access.
Related Links
Attachment 1 
Created BySumanto Chakraborty



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255