How can we verify that NICE CXone is successfully connected after completing all required configurations?
I attempted logging in through the phone panel, but I don’t see any related entries in the logs or Tracer.
For the OpenID configure URL, I have created an authentication service OpenID
To verify that NICE CXone is connected, open the phone panel in your Constellation application and try to sign in with a valid CXone user. If the connection is working, the panel should load successfully and show the agent state or phone options instead of staying blank or failing. Then check the browser developer tools Network tab and confirm that the CXone authentication and API calls are returning successful responses. In Pega, review the authentication service and confirm the OpenID configuration URL, client details, and redirect settings are correct. If the login completes and the CXone API calls succeed in the browser, the integration is connected properly.
Thanks, Rohit.
@Sairohith We are encountering an issue during the login flow. A pop-up appears prompting the user to log in, but after entering credentials, the page remains blank and the login does not complete.
From the browser developer tools, we can see that a 302 (Found) redirect is occurring during the authorization step. This suggests that the request is being redirected, but the flow is not completing as expected.
We have attached a screenshot for reference. Could you please confirm whether any additional configuration or handling is required on either side to complete the authentication flow?
Our DevOps has allowed the internet to pass through (pega talking to external applications )
The 302 redirect means the NICE CXone login is reaching the authorization step, but the callback is not being completed correctly in Pega. The blank page usually happens when the redirect URL returned by NICE does not exactly match the redirect or callback URL configured in the OpenID authentication service and the CXone setup. Please verify that the same callback URL is registered on both sides, including protocol, host name, path, and any expected response handling. Once that URL matches exactly, the token exchange should complete and the login flow should finish instead of stopping on a blank page.
@Sairohith We have verified that the redirect URI configuration is correct on both sides.
Earlier, when an incorrect redirect URL was used, we consistently received a clear error response indicating a mismatch. After updating it with the correct redirect URI, that error no longer occurs.
However, with the corrected configuration, the behavior has changed — the login flow now proceeds further, but results in a blank page after authentication, along with a 302 redirect observed during the authorization step.
below is the wrong redirect url error
hi @PramodD17632620 @Sairohith
I am also in same boat. trying to lunch cxone embedded panel in pega, but the configuration is giving me same error. “redirect_uri” parameter.
Any breakthrough on this issue?
What the value configured in open id url?
is it https://cxone.niceincontact.com or https://cxone.niceincontact.com/.well-known/openid-configuration
Hi @BukhariS5498
It’s all in the Nice CXone registration for your application. While you’re registering, we need to provide our redirect URL and authentication as OpenID. I am attaching a JSON object that clearly shows how to provide all required data.
Once you get back a JSON object from Nice, I am attaching a picture to configure the CTI rule
You can remove -gov from the URL if your client is not federal.
Nice implementation is done mostly if the authentication is successful. Once you log in to the Phone panel, a Nice cxone soft panel will appear.
One more important DSS needs to be updated if you’re using Constellation DSS -”ConstellationMessageSvcHostPath”
Follow the URL below for updating DSS
https://docs.pega.com/bundle/platform/page/platform/deployment/constellation/constellation-messaging-deploy-overview.html
Nice.txt (789 Bytes)
thank you @PramodD17632620 will try this and drop a note on how it goes.
