Enterprise Admin User Interface (EAUI)
The Visual UGC Embeddable Admin User Interface (EAUI) enables Visual UGC OEM partners to embed components of the Visual UGC Admin User Interface into whitelisted systems.
Key features of the EAUI include:
- Ability to embed a frameless version of the Visual UGC Admin User Interface into Whitelisted domains.
- Ability to manage user sessions within the EAUI iFrame, and perform SSO.
- Ability to apply custom ACL rules to the EAUI iFrame
- Ability to navigate to pages from outside of the EAUI iFrame
Visual UGC's EAUI offerings is available as a Plugin for OEM Partners. This plugin can be enabled for partners on their Development Stacks for the purpose of testing and building integrations.
After a developer has installed the plugin, they will be able to retrieve the OAuth information from Visual UGC to reveal the OAuth Access Token.
Before the integration, ensure that you've added the parent page domain to the permitted domain section in the configuration only use the domain name without the protocol. e.g. awesome.com or stackla.awesome.com (Please do not add the https:// value).
Note: The permitted domain will only be valid for a domain with an SSL certificate (HTTPS)
To embed Visual UGC into an existing web portal, please copy the embed code from the configuration page, and add it to the section of your portal where you would like to render the Visual UGC page.
An example of the Embed Code is available below:
In order for the Visual UGC EAUI to work, it requires an active Session Token. This token is tied to a specific user, and should be generated using OAuth.
As per the standard OAuth process, the steps involved to generate a session token are:
- Generate a Short Term Token
- Generate Access Token
- Generate a Session Token
The steps required are listed below.
Generate the Short Term token by calling the Visual UGC Authenticate API Endpoint and providing the
redirectUrland a relevant
// POST Request
Once the OAuth request has been made, a Short Term token will be provided in a format similar to below.
Taking the Short Term Token, a second request can be made to generate an Access Token. The Short Term token should be added to the
// POST Request
Assuming the Exchange is successful, the provided response will be contain the following attributes:
Access Tokens will, by default, expire every 365 days.
Final step in the process is now to generate the Session Token. This is done via the Access Token, by making a call to the OEM Session endpoint as per below.
// POST request
If the exchange Session Token is a success the response will contain the valid session token as data (see example below):
After obtaining the valid Session Token, a developer will need to add it to the embed code
[ADD_YOUR_SESSION_TOKEN]with valid Session Token).
Session tokens are only valid for one use and have a lifespan of 60 seconds.
Note: If there is a requirement to have a different landing page, you can provide the valid url page in the embed code as the data attribute
Manage Event Screens