By: Emma Richardson user 09 Apr 2019 at 6:57 a.m. CDT

1 Response
Emma Richardson gravatar
I have been struggling to set up SSO with our Freshdesk account. They have sent me an xml file which is being referenced correctly as SP1 in the metadata-providers.xml. In this folder (https://www.dropbox.com/sh/3itm5c2s41ls468/AAB7HpCqmYPIF9qXzE2R_Dfea?dl=0) are the two xml files (one working with Zoom.us and the non-working one with Freshdesk plus the metadata-providers.xml file showing reference to both files. Despite these appearing to be correct, I continue to get the following error: ``` 2019-04-09 11:39:44,314 - DEBUG [org.opensaml.saml.metadata.resolver.impl.AbstractMetadataResolver:434] - Metadata Resolver FilesystemMetadataResolver SiteSP1: Metadata backing store does not contain any EntityDescriptors with the ID: https://help.ecboces.org 2019-04-09 11:39:44,314 - DEBUG [org.opensaml.saml.metadata.resolver.impl.AbstractBatchMetadataResolver:162] - Metadata Resolver FilesystemMetadataResolver SiteSP1: Resolved 0 candidates via EntityIdCriterion: EntityIdCriterion [id=https://help.ecboces.org] 2019-04-09 11:39:44,315 - DEBUG [org.opensaml.saml.metadata.resolver.impl.AbstractMetadataResolver:586] - Metadata Resolver FilesystemMetadataResolver SiteSP1: Candidates iteration was empty, nothing to filter via predicates 2019-04-09 11:39:44,315 - DEBUG [org.opensaml.saml.metadata.resolver.impl.AbstractMetadataResolver:434] - Metadata Resolver FilesystemMetadataResolver SiteSP2: Metadata backing store does not contain any EntityDescriptors with the ID: https://help.ecboces.org 2019-04-09 11:39:44,315 - DEBUG [org.opensaml.saml.metadata.resolver.impl.AbstractBatchMetadataResolver:162] - Metadata Resolver FilesystemMetadataResolver SiteSP2: Resolved 0 candidates via EntityIdCriterion: EntityIdCriterion [id=https://help.ecboces.org] 2019-04-09 11:39:44,315 - DEBUG [org.opensaml.saml.metadata.resolver.impl.AbstractMetadataResolver:586] - Metadata Resolver FilesystemMetadataResolver SiteSP2: Candidates iteration was empty, nothing to filter via predicates 2019-04-09 11:39:44,316 - DEBUG [org.opensaml.saml.metadata.resolver.impl.PredicateRoleDescriptorResolver:260] - Resolved no EntityDescriptors via underlying MetadataResolver, returning empty collection 2019-04-09 11:39:44,316 - INFO [org.opensaml.saml.common.binding.impl.SAMLMetadataLookupHandler:128] - Message Handler: No metadata returned for https://help.ecboces.org in role {urn:oasis:names:tc:SAML:2.0:metadata}SPSSODescriptor with protocol urn:oasis:names:tc:SAML:$ 2019-04-09 11:39:44,317 - DEBUG [net.shibboleth.idp.profile.impl.WebFlowMessageHandlerAdaptor:174] - Profile Action WebFlowMessageHandlerAdaptor: Invoking message handler of type 'org.opensaml.saml.common.binding.impl.SAMLAddAttributeConsumingServiceHandler' on INBOUND m$ 2019-04-09 11:39:44,318 - DEBUG [net.shibboleth.idp.profile.impl.WebFlowMessageHandlerAdaptor:195] - Profile Action WebFlowMessageHandlerAdaptor: Invoking message handler on message context containing a message of type 'org.opensaml.saml.saml2.core.impl.AuthnRequestImpl' 2019-04-09 11:39:44,318 - DEBUG [org.opensaml.saml.common.binding.impl.SAMLAddAttributeConsumingServiceHandler:110] - Message Handler: No metadata context found, nothing to do 2019-04-09 11:39:44,319 - DEBUG [net.shibboleth.idp.saml.profile.impl.InitializeRelyingPartyContextFromSAMLPeer:132] - Profile Action InitializeRelyingPartyContextFromSAMLPeer: Attaching RelyingPartyContext based on SAML peer https://help.ecboces.org 2019-04-09 11:39:44,334 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:293] - Resolving relying party configuration 2019-04-09 11:39:44,337 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:299] - Profile request is unverified, returning configuration shibboleth.UnverifiedRelyingParty 2019-04-09 11:39:44,337 - DEBUG [net.shibboleth.idp.profile.impl.SelectRelyingPartyConfiguration:136] - Profile Action SelectRelyingPartyConfiguration: Found relying party configuration shibboleth.UnverifiedRelyingParty for request 2019-04-09 11:39:44,340 - WARN [net.shibboleth.idp.profile.impl.SelectProfileConfiguration:111] - Profile Action SelectProfileConfiguration: Profile http://shibboleth.net/ns/profiles/saml2/sso/browser is not available for RP configuration shibboleth.UnverifiedRelyingPart$ 2019-04-09 11:39:44,358 - WARN [org.opensaml.profile.action.impl.LogEvent:105] - A non-proceed event occurred while processing the request: InvalidProfileConfiguration 2019-04-09 11:39:44,359 - DEBUG [org.opensaml.saml.common.profile.logic.DefaultLocalErrorPredicate:154] - No SAMLBindingContext or binding URI available, error must be handled locally ``` Please help!

By Emma Richardson user 09 Apr 2019 at 11:34 a.m. CDT

Emma Richardson gravatar
Figured out that the request came in with https:// and this was not included in the xml file. Added that and finally got to log in screen.