Redirect user authentication to a Service Portal
-
- UpdatedFeb 1, 2024
- 1 minute read
- Washington DC
- Virtual Agent
After installing a pre-built Conversational Integration (for messaging apps, Consumer apps or voice apps), you can specify a Service Portal in which unauthenticated end users complete the user authentication step (user account linking), instead of in their ServiceNow instance. Users who do not have linked accounts complete authentication before continuing with the virtual agent in the messaging application.
Before you begin
Install the Virtual Agent messaging integrations for your instance. The system creates a record in the Provider Auth [provider_auth] table for each integration that you install (Slack, Microsoft Teams, and Workplace, LINE, Twilio, WhatsApp, Facebook Messenger, Alexa, Google Assistant, Amazon Connect). You use the Provider Auth table to specify the Service Portal in which user authentication occurs.
Role required: admin
Procedure
- In the navigation filter, type provider_auth.list.
- In the Provider Auth table, open the record for the messaging integration you installed.
- In the Service Portal field, select the Service Portal in which user authentication occurs.
- Click Update.
Result
When unauthenticated users start a conversation with the virtual agent for the first time in the messaging integration, they are redirected to the Service Portal specified for the provider in the Provider Auth table. After they log in to the Service Portal, they are prompted to link their ServiceNow account to the messaging application.