How do I integrate Avacaster login with another registration system?
From Avacast Support
How do I integrate Avacaster login with another registration system?
IMPORTANT: Customers are strongly encouraged to plan and implement the following options for authentication before creating a lot of events on the Avacaster server, otherwise there will be extra work required later to update existing events.
There are currently two options for integrating with another registration system. In both cases, you do not register users within Avacaster at all, but rather use Avacaster's external Login Style (defined on the Adminstrator Setup panel). Depending on your preference, you have the option to either:
Option A: Set certain cookies that the Player will check to verify that the user is authorized for an event.
Option B: Have the Player call a special page on the registration system that basically confirms whether this user is authorized for an event.
Whether you use method A or B, the following is true:
- To use either option, someone must write the proper code on the registration server, and in some cases, Avacast must modify a configuration file on the Avacaster server.
- It is assumed that the user has already logged in to your registration system before launching the Avacaster Player, and has either established some sort of server session, or has set the appropriate cookies.
- If a particular username is registered in both the external system and the Avacaster Administrator Users Panel for that event, the password in both systems must be the same, or else login will fail.
- In order to avoid Flash and Shockwave security issues, you should define a subdomain name pointing to the Avacaster server that is in the same domain as your registration server (e.g. something like avacast.yourdomain.com). URL references in your Avacaster events must then be changed to use this new name.
- For Flash 7+ users, you must create a proper crossdomain.xml file and place it on the server containing the authentication page (if using that method), or else access will never be possible. Note that this allows you to use servers in different domains; however, Flash 6 does not use this file, meaning you must still use servers in the same domain if you wish to support Flash 6 users.
- Option B only: Your event names must start with one or more predefined prefixes, in order to better control which events utilize this type of authentication. Such a prefix must be agreed upon before the server can be configured, and thus before you create any events that use this method.
For more detailed information, refer to the article below. Only designated Avacast Support staff can view this article. Customers interested in using external login should contact Avacast Support.
How do I set up external login?
NOTE:
Avacaster database integration is currrently in development and will provide more a convenient option. A release date has not yet been finalized.
Also, another alternative may be a beta version the Avacaster SOAP API, which includes an option to add users to a particular event's User roster. Thus an external system could add users as needed to the Avacaster event itself, in which case the password login style would be used. Note that since this is beta software, the required server scripts are not part of Avacaster production version 4.1.x, meaning these scripts must be installed manually on a server in order to use this option. To inquire about possibly using this beta software, contact Avacast Support. For more information about the available SOAP functions, refer to the following document:
