[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-01 UTC。"],[[["\u003cp\u003eThis guide provides instructions for setting up a proxy server to simplify authentication with the Dialogflow API, in conjunction with an application server.\u003c/p\u003e\n"],["\u003cp\u003eBoth an application server and a proxy server must be deployed in the same directory before the modules can be rendered in LivePerson.\u003c/p\u003e\n"],["\u003cp\u003eDeployment of the proxy server can be done on any hosting platform, but the instructions specifically use Google's Cloud Run service.\u003c/p\u003e\n"],["\u003cp\u003eSeveral environment variables, such as \u003ccode\u003eLP_ACCOUNT_ID\u003c/code\u003e, \u003ccode\u003eLP_SENTINEL_DOMAIN\u003c/code\u003e, and \u003ccode\u003eJWT_SECRET\u003c/code\u003e, need to be configured during the deployment process.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eDF_PROXY_SERVER_URL\u003c/code\u003e environment variable for the application server must be set using the outputted URL (\u003ccode\u003etarget_url\u003c/code\u003e) after the proxy server is deployed.\u003c/p\u003e\n"]]],[],null,["# Deploy the proxy server\n\nThis guide outlines the steps required to set up a proxy server. You will use\nthe proxy server in conjunction with an\n[application server](/agent-assist/docs/liveperson-application) to simplify\nauthentication with the Dialogflow API. For instructions on rendering the UI\nmodules in the agent workspace, see the\n[main LivePerson tutorial page](/agent-assist/docs/liveperson). Both an\napplication server and a proxy server in the same directory are required before\nyou can render the modules in LivePerson.\n\nAlthough it is possible to set up this integration deployment on any hosting\nplatform, these instructions use Google's\n[Cloud Run](https://cloud.google.com/run/docs).\n\nBefore you begin\n----------------\n\nMake sure that you have already\n[deployed the application server](/agent-assist/docs/liveperson-application)\nbefore you start this tutorial.\n\nConfiguration\n-------------\n\nWhen you deploy the service, you must define following environment variables.\nMake sure to leave the `LP_CLIENT_ID` and `LP_CLIENT_SECRET` variables blank\nwhen you initially create the application server. LivePerson will provide\nthese variables when you\n[create a Conversational Cloud application](/agent-assist/docs/liveperson#install_a_conversational_cloud_application),\nand you will update them at that time. You will also initially skip\n`APPLICATION_SERVER_URL` and `DF_PROXY_SERVER_URL`, setting both after the\napplication and proxy servers have been deployed and returned the required\nvalues.\n\n- `LP_ACCOUNT_ID`: LivePerson account ID.\n- `LP_CLIENT_ID`: Your LivePerson client ID. This will be provided by LivePerson once the Conversational Cloud application has been installed. (Skip this variable for now, you will update it once the information has been provided).\n- `LP_CLIENT_SECRET`: Your LivePerson client secret. This will be provided by LivePerson once the Conversational Cloud application has been installed. (Skip this variable for now, you will update it once the information has been provided).\n- `LP_SENTINEL_DOMAIN`: Go to https://developers.liveperson.com/domain-api.html. Enter your account number and look up the domain for \"sentinel\".\n- `LP_ACCOUNT_CONFIG_READONLY_DOMAIN`: Go to https://developers.liveperson.com/domain-api.html. Enter your account number and look up the domain for \"`accountConfigReadOnly`\".\n- `APPLICATION_SERVER_URL`: URL of the UI application server.\n- `JWT_SECRET`: A \"secret\" phrase that will be used to sign the authentication tokens. You can use any phrase, although a long, random secret is most secure. Please see best practices at https://fusionauth.io/learn/expert-advice/tokens/building-a-secure-jwt/#keys.\n\nSample `.env` file: \n\n LP_ACCOUNT_ID = 12345678\n LP_CLIENT_ID = abc-123-f0f0\n LP_CLIENT_SECRET = abc123abc123abc123abc123\n LP_SENTINEL_DOMAIN = va.sentinel.liveperson.net\n LP_ACCOUNT_CONFIG_READONLY_DOMAIN = z1.acr.liveperson.net\n APPLICATION_SERVER_URL = https://my-project.wm.r.appspot.com\n JWT_SECRET = an_example_JWT_secret_phrase_please_use_something_better\n\nDeploy\n------\n\nThe UI application server must be deployed to a Google Cloud hosting service.\nWe recommend using either Google App Engine or Cloud Run. The steps below use\nCloud Run as an example.\n\n### Deploy using CLI\n\nIn your local terminal, change the active directory to the repository's root\ndirectory.\n\nRun the following command to save the state of your repository into\n[Google Cloud Platform Container Registry](https://console.cloud.google.com/gcr/images). Replace\n`PROJECT-ID` with your Google Cloud Platform project ID. \n\n gcloud builds submit --tag gcr.io/PROJECT-ID/agent-assist-modules-proxy-server\n\nDeploy your integration to live using the following command. Replace\n`PROJECT-ID` with your agent's Google Cloud Platform project ID, and\n`SERVICE-ACCOUNT-EMAIL` with your service account client email. \n\n gcloud run deploy --image gcr.io/PROJECT-ID/agent-assist-modules-proxy-server --service-account=SERVICE-ACCOUNT-EMAIL --memory 1Gi --platform managed\n\n- When prompted for a region, select a region (for example, `us-central1`).\n- When prompted for a service name hit enter to accept the default.\n- When prompted to allow unauthenticated invocations press `y`.\n\nFor more information, see the [Cloud Run documentation](/run/docs/deploying).\nYou can view a list of your active integration deployments under\n[Cloud Run](https://console.cloud.google.com/run) in the Google Cloud Platform Console.\n\n### Environment variables\n\nFollow the [Cloud Run instructions](/run/docs/configuring/environment-variables)\nto set the necessary environment variables.\n\nOnce the service has been deployed, the CLI will output the URL that the\napplication was deployed to (`target_url`). Go back and set the\n`DF_PROXY_SERVER_URL` environment variable for the **application server** using\nthis value.\n\n### Shut down the proxy server\n\nTo shut down the application server, you need to delete the Cloud Run service.\n\nIn your local terminal, run the following command and select the previously\nchosen target platform to list active deployments: \n\n gcloud beta run services list\n\nNext, run the following command: \n\n gcloud beta run services delete agent-assist-modules-proxy-server"]]
