Overview

This article provides guidance on testing and troubleshooting the SAML Single Sign-On (SSO) setup for PostBeyond, including steps to verify correct implementation and resolving common errors. It emphasizes the importance of checking the setup details such as Entity IDP, login page, and service endpoints, and offers solutions for specific issues like user assignment across multiple organizations and incorrect URL entries. The article also invites users to contact PostBeyond support for further assistance and provides integration guides for various applications with OKTA.

Information

Testing and Troubleshooting

After you have set up your SSO, test to ensure that it is working correctly by creating a user and having them log in to their account via SSO.

Should you notice that something is wrong...

Have your team go back and make sure that the set-up is correct. This includes, but is not limited to making sure that the following have been added correctly: the Entity IDP, the login page, and the service endpoints.

Please notify the PostBeyond team: we too will make sure that our set-up is correct by going through the process again.

If the issue persists, please send PostBeyond a HAR file.

Potential Errors and How to Resolve Them

Below are potential errors that you might be experiencing. Please review carefully to see if this could be causing issues for your SSO login:

Assigning Users to Applications

Issue: More than one Organization

If the customer has users in more than one organization, (i.e., Company A bought Company B - so while it's one customer, they are working with two separate organizations and IT systems), and a user receives the below error message when trying to access PostBeyond through SSO login:

Solution: You should check that the user management system (i.e., the IdP) has granted that user access to PostBeyond using SAML SSO integration/setup. In the example above, Company A was not granted access from Company B to use PostBeyond and the Company B IT team had to go back and grant this permission.

Short URL Added is Not in Complete Form

Issue: If you enter a short URL like postbeyond.social and not share.postbeyond.social, you will get the following error:

Solution: Add the complete URL.

If you do not see the error message you are experiencing above, please send an email to support@postbeyond.com with a screenshot of the error, and we will help you out with your investigation!

Integration Guides

Below are guides to help you integrate various applications with OKTA for Single Sign-On (SSO) functionalities:

FAQ

What should I do if users from multiple organizations cannot access PostBeyond through SSO?

Check that the user management system has granted the user access to PostBeyond using SAML SSO integration. Permissions may need to be adjusted if users belong to different organizations within the same customer entity.

What is a common error when entering a URL during SSO setup and how can it be resolved?

A common error is entering a short URL such as "postbeyond.social" instead of the complete form "share.postbeyond.social". To resolve this, ensure you add the complete URL.

Who should I contact if I encounter an error that is not listed in the article?

If the error message you are experiencing is not mentioned, you can email support@postbeyond.com with a screenshot of the error for further assistance.

How can I test if my SSO setup is working correctly with PostBeyond?

Create a user and have them log in to their account via SSO to test if the setup is working correctly. If there are issues, review the setup details and contact PostBeyond support if needed.

What should I do if I continue to experience issues after verifying the SSO setup?

If issues persist after checking the setup, send a HAR file to PostBeyond for further analysis and troubleshooting.