New to the community? Start here

[The Hub Client] Give WordPress Users Access

1

I use a WP site as a client portal so to speak. There are support plugins, payment/checkout plugins (WooCommerce), etc. so it makes sense. I’ve been trying to figure out how to let members log into their sites managed by me through the portal. This way they only need to memorize a single login to access support, billing, and their site if needed.

The Hub Client looks like it could be the missing piece for me, but as of now the login is separate from WordPress. If the WordPress users were synced or there was a way for them to SSO into the /hub/ part of the site that’d be perfect.

To clarify, right now a user logged into WordPress could access /hub/ but they’d be presented with the WPMU Dev login (whitelabeled) so they have to login “again” so to speak. I understand it is two different systems, but from the end user perspective they wouldn’t necessarily realize.

Mon, 28 Sep 2020 12:05:15
More The Hub Client discussions
The Hub Client
  • benprice
    • Site Builder, Child of Zeus

    We just had an extended discussion about an approach that should work for you although different than the one you suggest. IWPMUDev is working on a feature request that should do what you request functionally. I will dig up the link and post it here if no one else does before I get back to you.

  • Patrick Freitas
    • FLS

    Hi Ben

    I hope you are doing well.

    Thank you for the suggestion.

    Yes, HUB will work outside of WordPress login, it requires a connection to the WPMU DEV API to authenticate the users.

    We are already working on a feature to allow the HUB users to use the SSO from HUB to their website, currently, only the team owner would be able.

    However, I’m afraid as the HUB users don’t use the WordPress users it wouldn’t be able the auto-login using the WordPress dashboard directly to the HUB.

    Best Regards
    Patrick Freitas

  • Glenton
    • Site Builder, Child of Zeus

    Today marks 2 years (4/3/2023) since I posted about this terrible flaw in the customer user journey. The fact that you raised the same issue 3 years before that, and there isn’t so much as a mention on their roadmap, is insane.

    It’s been five years without a fix. I gave up about a year ago. I had another WPMUDEV subscription for a productized WordPress service that required SSO authentication. I built my custom solution using Runcloud’s Magic Link API within that time. It only took three months of work.

    This is not a complex problem to solve. WHMCS has had this feature since 2018, and it’s not even a WordPress-specific platform. New services like Dollie offer this out-of-the-box and work with internal and external hosted sites.

    At this point, I only use my WPMUDEV subscription for a few of their plugins. Outside of that, there is no reason to use any of their Reseller products, as they can’t be integrated with anything.

    No SSO, no APIs, no webhooks, nothing.

    How is your tagline “Made for web developers, by web developers.”

    The platform is a black box; using it in its current state would involve adding a bunch of manual steps to your current workflow if you’re already running an agency. It’s OK if you’re new.

    PS: I’ve been a WPMUDEV customer for over 10 years.

  • Luis Soriano
    • Staff

    Hi Glenton

    Hope you are doing fine!

    Thank you for reaching out and sharing your concerns regarding the delay in the implementation of the requested HUB SSO feature. We understand how frustrating it can be to wait for a functionality that is important to your workflow, especially when it has been anticipated for a significant amount of time. Your patience and continued use of some of our plugins is greatly appreciated, and we want to assure you that your feedback has not gone unnoticed.

    One of the primary reasons for the extended timeline is our commitment to ensuring that all new features meet the highest standards of security. In today’s digital environment, it is crucial that we thoroughly assess and test every feature to protect your data and maintain theof the overall system. Rushing development without the necessary safeguards could potentially introduce vulnerabilities, and we want to avoid putting our members operations at risk.

    Additionally, compatibility is another major factor that adds complexity to the development process. Keep in mind, the HUB connects to a wide range of environments and configurations, and we need to ensure that any new feature works seamlessly for all users—regardless of their setup. This requires extensive testing, development iterations, and sometimes even architectural adjustments, all of which have contribute to add more time to the development of this feature.

    We remain committed to delivering a robust and reliable solution, and be certain that your feedback continues to play a crucial role in our development priorities. I have also shared this information to the HUB development team so they are aware of our members interest in this feature.

    Please feel free to reply if you’d like to add any additional insights related to this matter.

    Kind regards

    Luis