By: Harrison Dragoo user 23 Jan 2017 at 9:26 a.m. CST

3 Responses
Harrison Dragoo gravatar
I am attempting to setup saml 2.0 with Blackboard however when testing the setup that I have I am given the following error from the Gluu server before being presented with a login page: ERROR An error occurred while processing your request. Please contact your helpdesk or user ID office for assistance. This service requires cookies. Please ensure cookies are enabled in your browser, then go back to your desired resource and try to login again. Use of your browser's back button may cause specific errors that can be resolved by going back to your desired resource and trying to login again. If you think you were sent here in error, please contact technical support Error Message: SAML 2 SSO profile is not configured for relying party https://MY.HOSTNAME/idp/shibboleth

By Harrison Dragoo user 23 Jan 2017 at 10:42 a.m. CST

Harrison Dragoo gravatar
we are no longer getting that error now we are getting. ERROR An error occurred while processing your request. Please contact your helpdesk or user ID office for assistance. This service requires cookies. Please ensure cookies are enabled in your browser, then go back to your desired resource and try to login again. Use of your browser's back button may cause specific errors that can be resolved by going back to your desired resource and trying to login again. If you think you were sent here in error, please contact technical support Error Message: No peer endpoint available to which to send SAML response

By Harrison Dragoo user 23 Jan 2017 at 10:47 a.m. CST

Harrison Dragoo gravatar
The above error happens after login

By Mohib Zico staff 23 Jan 2017 at 4:33 p.m. CST

Mohib Zico gravatar
Hello Harrison, >> An error occurred while processing your request. Please contact your helpdesk or user ID office for assistance. I think these are coming from SP side; so you might wanna ask them for any interesting stack trace. From Gluu Server side, you just need to make sure that.. your Gluu Server is sending proper information to SP. To check that you can enable Shibboleth logging to DEBUG and check for SAML assertion; see if all scopes/attributes, required nameID and destination url are good ornot.