By: Emma Richardson user 03 Apr 2019 at 11:10 a.m. CDT

2 Responses
Emma Richardson gravatar
Apparently my ticket got closed so starting a new one. To follow up on process previously reported here: [https://support.gluu.org/single-sign-on/6891/saml-non-ok-status-code-500-returned-from-remote-metadata-source/ ](http://) I changed the settings on Freshdesk to point to the HTTP-Redirect instead of http-post. I am now receiving the following messages in idp process ``` 2019-04-03 15:54:33,845 - 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-03 15:54:33,846 - 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-03 15:54:33,846 - DEBUG [org.opensaml.saml.common.binding.impl.SAMLAddAttributeConsumingServiceHandler:110] - Message Handler: No metadata context found, nothing to do 2019-04-03 15:54:33,856 - DEBUG [net.shibboleth.idp.saml.profile.impl.InitializeRelyingPartyContextFromSAMLPeer:132] - Profile Action InitializeRelyingPartyContextFromSAMLPeer: Attaching RelyingPartyContext based on SAML peer https://ecboces.freshdesk.com 2019-04-03 15:54:33,862 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:293] - Resolving relying party configuration 2019-04-03 15:54:33,863 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:299] - Profile request is unverified, returning configuration shibboleth.UnverifiedRelyingParty 2019-04-03 15:54:33,864 - DEBUG [net.shibboleth.idp.profile.impl.SelectRelyingPartyConfiguration:136] - Profile Action SelectRelyingPartyConfiguration: Found relying party configuration shibboleth.UnverifiedRelyingParty for request 2019-04-03 15:54:33,870 - 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-03 15:54:33,878 - WARN [org.opensaml.profile.action.impl.LogEvent:105] - A non-proceed event occurred while processing the request: InvalidProfileConfiguration 2019-04-03 15:54:33,879 - DEBUG [org.opensaml.saml.common.profile.logic.DefaultLocalErrorPredicate:154] - No SAMLBindingContext or binding URI available, error must be handled locally ``` In the browser, I am receiving "Web Login Service - Unsupported Request The application you have accessed is not registered for use with this service. "

By Emma Richardson user 03 Apr 2019 at 2:01 p.m. CDT

Emma Richardson gravatar
After talking with Freshdesk, we noticed that they are sending a GET and they need to know if the request needs to be in a specific format?

By Emma Richardson user 04 Apr 2019 at 1:01 p.m. CDT

Emma Richardson gravatar
Or is there a way to set up Gluu to respond to a GET request instead of a POST request?