Deploying the Jive SBS Public 6 Application Results in Redirect to Okta Portal Skip to main content
https://support.okta.com/help/blogdetail?id=a67f0000000bln6iai&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fblogdetail
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.

Deploying the Jive SBS Public 6 Application Results in Redirect to Okta Portal

Oct 12, 2015 | by Thomas Hill in Security

Original Author: Joe Gazarik, Okta

Problem

You are not able to deploy the Jive SBS Public 6 application in Okta using SAML authentication

Symptoms

When you deploy the Jive SBS Public 6 OAN application in Okta and use SAML, authentication attempts result in a redirect back to the user's Okta portal page instead of into the Jive landing page

Cause

This behavior is caused by the SSO Service Bindings not matching between Okta and Jive.  Okta's OAN integration with Jive is written to use an HTTP GET Redirect while Jive by default is configured to use HTTP POST.

Resolution

To resolve this problem and utilize the full capabilities of the Jive SBS 6 OAN application (including full downstream user management), change the SSO Service Binding in your Jive configuration from HTTP POST, to HTTP Get Redirect.  Jive documents how to do this here: Jive 6.0 Community Administrator Documentation under the SSO Service Binding section. 

Comments