I am working on a project where a client would like to be able to have a single sign on system for Mashery, a forum built on phpBB and a CMS built on Joomla. They would like the username and password to be consistent across all systems. To accomplish this, I need a way to capture a username and password before it gets into Mashery to be able to create the user in phpBB, and then create the user in Mashery. This also needs to be done when logging in (automate login to phpBB), as well as when a user does something like update their profile or password.
In looking at the Mashery documentation, I am having a hard time determining if this is possible. Is there a way to automate user registration or login through a Mashery API, allowing us to create custom pages? I could automate an HTTP Post to the Mashery registration page (in our case /member/register), but this feels like a bit of a hack to me.
Any suggestions? I hope I explained what I am trying to accomplish well enough :)
Message edited by Justin Gasper 4 years ago
4 years ago
We have several ways to do SSO and integrate with external sites.
You may have noticed when you login that you are taken to the secure.mashery.com domain for login. This domain is our identity providing domain. We use this to implement single sign in for a mashery account across our customer's domains. This allows existing mashery accounts to login to non-mashery domains. The protocol used is SAML. Setting it up requires using a Mashery provided certificate and a review process.
Another way to implement SSO is for Mashery to use an external identity provider. In this model, our Sign In link will redirect to an external domain and an account will be created when a new member is logged in. This also uses the SAML protocol and is our most common way of implementing SSO. In this process, account registration is done on an external site and user information is passed as part of the SAML protocol.
Additionally, we provide an API so that you can create new users and manage user information.
We have another feature, callbacks, which aids in synchronizing data. With callbacks, we can call an external API call whenever a key, application, or member is created, updated or deleted in our system.
We also have an extension page feature which allows content from external sites to be seamlessly integrated into the portal.
Changing SSO options for an existing customer can involve special considerations and migration.
Each of these options requires that they be enabled for the customer using them. If your client is a current Mashery customer, then the best thing to do would be to have them contact their Customer Support Manager to discuss which option would be best. You can also contact us at firstname.lastname@example.org to get that process started.
Please sign in to add a post.