The combination of the client-side singleSignOn API and the server-side getSingleSignOnToken API allows for external web services with username/password authentication services to extend these credentials to Convio hosted pages where the non-Convio web service operates as the master authenticator. In other words, if your organization has another web presence where visitors are required to login to gain access (e.g. non-Convio CMS) this API allows you to pass a token over to Convio which then honors the users credentials and grants them access as if they were to have logged in to your Convio hosted pages.
Q: Can the APIs support Convio as the master authenticator and my external system as the "client" of Convio?A: Not at this time. Using these APIs assumes the third-party system is the master authenticator.
Got more questions you want answered? Complete the form below. Want to discuss best practices, share or find client code samples and ask support questions? Visit the online community.
Visit the Community to chat with other clients and partners using the APIs and share code snippets.
