Integrating External Data with X-Pages
Content developers can create X-Pages content that integrates data and real-time services from external applications in a secure way, using Vault Session ID or SSO authentication. This allows users to view data from Vault CRM and external sources combined without navigating away from the Vault CRM app to authenticate to the external source.
For example, a content developer creates an X-Page that displays data from an internal chat bot. Since the information is from their own system, values are displayed in real-time.
Who can use this feature?
- Content Developers - Browser
- Enabling X-Pages Integration with External Applications
- Studio Admin Users - Browser
- Viewing Activity Logs
- End Users - Browser, iPad, iPhone
- Using X-Pages Integrated with External Applications
- Users do not require an additional license
Configuring X-Pages Integration with External Applications for
All Users
This configuration applies to SSO authentication only. Vault Session ID authentication does not require configuration.
To configure this feature:
- EnsureConfiguring X-Pages is complete.
- Navigate to Business Admin > Objects.
- Select xpages_sso_configuration__v.
- Select Create.
-
Select a Status. Default is Active.
- Enter the following information as found in your SSO configuration:
- API name
- Authentication endpoint
- Token endpoint
- Client ID
- Client secret
- Select Save.
- Copy and add the Authentication Redirect URI to your SSO configuration.
Enabling X-Pages Integration with External Applications as
Content Developers
Content developers can use either of the following request methods to access data from the specified external application directly from an X-Page. External connections in Vault can be authenticated using a Vault Session ID or SSO access token.
Using Vault Session ID Authentication
X-Pages content developers can use the getVaultSessionId method to retrieve a valid session ID that can be used to communicate with Vault APIs or passed through a customer-defined authentication process for the external application.
Using SSO Authentication
If the external application uses OAuth-based SSO, content developers can use the getSSOAccessToken method to retrieve a valid access token that can be passed through a customer-defined authentication process for the external application.
Vault CRM and the external application must use the same SSO provider.
Viewing Activity Logs as
Studio Admin Users
Studio Admins can view information about session IDs or access token requests in the Activity Log to ensure only appropriate X-Pages content is using them.
Using X-Pages Integrated with External Applications as
End Users
End users can view data from Vault CRM and external sources combined without navigating away from the Vault CRM app to authenticate to the external source.
