anukasha

Hi Christina,

Thanks for reaching out to us.

As discussed over the Helpdesk Ticket, this issue was introduced by a conflict with an older version of the “Content Aware Sidebars” plugin.

Updating the Content Aware Sidebars plugin seems to have resolved the issue for you. We recommend keeping plugins updated to avoid any such issues in the future.

Feel free to reach out to us if you require any further?assistance.

Thanks,
Anukasha

Hi there,

Thanks for reaching out to us.

We are unable to reproduce the issue you mentioned. Additionally, we checked the line number of the error message and could confirm that the function on that line number is always called with the correct number of arguments.

Hence, we would need some further information like the SAML Tracer Logs and the Plugin Configurations to get to the root cause of this issue.
Please do reach out to us using the plugin’s support form so that we can debug further with this information.

Also, please let us know if you have made any modifications to the plugin code so that we can check the issue accordingly.

Thanks,
Anukasha

Hi there,

We sincerely apologize for the inconvenience you’ve experienced due to the recent update to version 1.5.4 of our plugin. We understand the frustration that comes with losing settings and authentication functionality, and we appreciate your patience as we address this matter.

Upon investigating the issue, we have promptly rolled back the problematic version of the plugin, ensuring that the disruptions caused are mitigated. Furthermore, we want to assure you that we are actively working on an improved release, which not only addresses the issues you encountered but also introduces new features, including support for SAML Protocol, SCIM User Provisioning, and more.

We would also like to offer our assistance in configuring the plugin for you. For this, we can schedule a quick Zoom or Google meeting at your convenience to guide you through the process. Please reach out to us from the plugin’s support form or from here, and we will coordinate a meeting accordingly.

Once again, we apologize for any inconvenience caused and appreciate your understanding. Your feedback is invaluable to us as we strive to enhance our services and provide you with a more reliable experience.

Thanks

Hi there,

We sincerely apologize for the inconvenience you’ve experienced due to the recent update to version 1.5.4 of our plugin. We understand the frustration that comes with losing settings and authentication functionality, and we appreciate your patience as we address this matter.

Upon investigating the issue, we have promptly rolled back the problematic version of the plugin, ensuring that the disruptions caused are mitigated. Furthermore, we want to assure you that we are actively working on an improved release, which not only addresses the issues you encountered but also introduces new features, including support for SAML Protocol, SCIM User Provisioning, and more.

We would also like to offer our assistance in configuring the plugin for you. For this, we can schedule a quick Zoom or Google meeting at your convenience to guide you through the process. Please reach out to us from the plugin’s support form or from here, and we will coordinate a meeting accordingly.

Once again, we apologize for any inconvenience caused and appreciate your understanding. Your feedback is invaluable to us as we strive to enhance our services and provide you with a more reliable experience.

Thanks

Hello James,

Thanks for reaching out to us.

I would like to inform you that you do not need to disable the AD integration for implementing SSO on your WordPress site using the MiniOrange SAML SSO Plugin i.e., you can use both simultaneously on your WP site for testing.

Feel free to reach out via the plugin’s support form if you have any questions or need any further assistance.

Thanks,
miniOrange

Hi @tekbird,

Thanks for reaching out to us.

We were not able to reproduce the issue you mentioned.
To reproduce the exact issue, could you please let us know the plugin version of the REST API Plugin that is currently installed on your site?

Also, it would be great if you could reach out to us via the plugin’s support form so that we can schedule a call with you to get this issue resolved at the earliest.

Thanks,
Anukasha

Hi @marcus182,

Thanks for reaching out to us!

It looks like you wish to enable SSO for your Freshdesk portal for your end-users such that, once logged in to the WordPress site, they should be able to SSO into the Freshdesk portal without having to authenticate again.

This is one of the Premium features of our other plugin – Login using WordPress Users [ https://www.ads-software.com/plugins/miniorange-wp-as-saml-idp/ ]. The feature is known as IDP-initiated Single Sign-On which would allow your users to directly click on a link from the WordPress site itself and they will be automatically logged in to the Freshdesk portal.

Please feel free to reach out to us via the Support Form in the plugin so that we can schedule a free demo of the Premium version.

Thanks,
miniOrange

• This reply was modified 1 year, 1 month ago by anukasha.

Hi there,

Thank you for reaching out to us.
We can definitely help you resolve this issue.

From the error message, it seems the error was received from your server/hosting provider since the plugin does not throw this error.

However, to understand the exact cause of the issue, can you please share the following details with us?

• SAML?Tracer?Logs?while reproducing the issue.
• Plugin configuration – You can click on Export Plugin Configuration in the miniOrange SAML SSO Plugin > Service Provider Setup?tab.

Please feel free to contact us via the Support form in the plugin so we can schedule a call with you to resolve this issue as soon as possible.

Waiting?to hear from you.

Thanks,
miniOrange

Hi,?

Thanks for reaching out to us.

After a thorough review, it appears that the images you mentioned do not exist within our WordPress SAML SSO Plugin. We also used a dead link checker with our plugin to verify that there are no images missing.

I would like to mention that all the images you mentioned are in .png format, whereas all the latest versions of our plugin have images in .webp format. Hence, it might?be possible you’re still using the older version?of the plugin.

Can you confirm that you have properly installed the latest version of our plugin v5.0.7?

If you are facing issues even after re-installation, please feel free to reach out to us via the support form in the plugin. We’d be be glad to help you resolve the issue.

Thanks, miniOrange Team

Hi there,

Thanks for reaching out to us.

I would like to let you know that our plugin enables the SSO between your WordPress site and your Identity Provider which automatically creates users in your WordPress Site during the SSO process. However, this should not impact any pages or posts when a user is deleted.

Could you please provide us with more details about the author who left your organization? Did you delete the user from the WordPress site or your Identity Provider? 

Please feel free to reach out to us from the support form given in the plugin settings so that we can schedule an online meeting with you and debug this issue at the earliest.

Thanks, Anukasha

Hi David,

Thanks for reaching out to us.?

Yes, the use case that you mentioned can be achieved using our plugin. You can add an SSO button on the WP login page which gives the flexibility to choose whether the user wants to use the SSO functionality or login through their WP Credentials.

If you are interested, we would be more than happy to provide you with a demo of our plugin. Please feel free to reach out to us from the support form given in the plugin settings so that we can schedule a demo with you.

Thanks,

miniOrange

Hi Oanah,

Thanks for reaching out to us.

We have tested our WordPress SAML Single Sign On (SSO) Plugin with Elementor and tried to edit a post, however, we couldn’t reproduce the issue you are mentioning.

I would like to mention that the plugin has been working flawlessly with Elementor for multiple customers.

However, we would be glad to help you further with this. Please let us know the versions of the WordPress SAML SSO and the Elementor Plugin so that we can check the issue in your exact settings.

Please feel free to reach out to us from the support form given in the plugin settings so that we can schedule an online meeting with you and debug this issue at the earliest.

Feel free to reach out if you have any concerns.

Thanks,

miniOrange

Hi there,

Thanks for pointing out this issue to us.

We were not able to reproduce this issue locally in our environments, however, we have made changes in the latest release of our plugin, v1.3.3 which would not cause such an issue.

We request you to kindly update to the latest version of the plugin.

Please do reach out to us from the support form in the plugin if you have any further questions.

Thanks

Hi there,

Thanks for pointing out the Page Restrict Access issue. This issue was resolved in the release v1.3.2. We request you update to the latest version.

We do provide the functionality to restrict Nav Menu Items in the pro version. You can restrict the Nav Menu Items from the Nav Menu Settings or use a toggle to hide all pages (which are restricted) in the Nav Menu Item.

In the Pro version, you can redirect the user to any page link when they try to access a restricted page. Hence, you can redirect to a 404 page as well.

As you are using SAML Single Sign On Plugin, I would like to mention that you can restrict the pages behind Single Sign On such that users are redirected to the Identity Provider (IDP) login page if they are not authenticated with the IDP.  

Please feel free to reach out to us using the support form (you can find it on our plugin) if you have any further concerns or questions.

Thanks

• This reply was modified 1 year, 11 months ago by anukasha.

Hi there,

Thanks for pointing out this issue. The problem you encountered was resolved in the new release v1.3.2. We request you update to the newer version.

Please reach out to us if you have any further concerns.

Thanks,
Anukasha