Issue while connecting Demo app with Partner Messaging

[simran-concret]

Hello Team,

As per Partner Messaging Documentation are testing out Interaction service inbound and outbound messages with Demo app but we are stuck while setting up please advise.

1. We have some doubts while configs the vars to the .env file -
   END_USER_CLIENT_IDENTIFIER : what should be the value for it? We tried giving some arbitrary value though.
   

2. We have installed the Partner Messaging package(created as per the instructions) in client org and now we are communicating this client org to Demo app, so the rest of the below parameters we have setup as per client org details like SF_ORG_ID, INSTACE_URL, consumer Key, SF_SCRT_INSTANCE but while starting the localhost server we are getting below error attaching our env file screenshot for your reference, please advise what could be the reason for this error.

Env file configuration:

Thanks ,
Simran

[dmadhwani]

END_USER_CLIENT_IDENTIFIER can be any id by which you identify your user uniquely. forexample phonenumber/username or any other id which you have to identify user uniquely

[dmadhwani]

also if you are facing any issue in your setup. you can open investigation with salesforce so someone from our team can help take a look at your org configurations if needed.
And we can verify if you have not missed any step from setup like

1. making sure messaging channel is active
2. making sure Read and Create permissions are given to your events for SCRT2 integration user perm set

[simran-concret]

Hi @dmadhwani , we have check setup of PMS from our end its looks good, only thing we updated .env file and starting the demo app server, then we are getting error,

Also we have raised case with salesforce FYR: please let me know if its works and we can connect today to troubleshoot if possible.
https://help.salesforce.com/s/case-view?caseId=500Hx00000W37aQIAR

Thanks..

[dmadhwani]

@james-wang-sfdc is our trust hero this sprint so he should be able to help you.

[simran-concret]

Hi @james-wang-sfdc , please let me know if we can connect today as per your availabilty to troubleshoot the issue. Thanks

[simran-concret]

Hi @dmadhwani , @james-wang-sfdc please let us know if we can connect to troubleshoot the issue as we are block with this.

Thanks in advance!!

[simran-concret]

Hi @dmadhwani , @james-wang-sfdc please let us know if we can connect today to troubleshoot the issue.
Thanks!!

[simran-concret]

Hi @dmadhwani , @james-wang-sfdc please let us know if we can connect to troubleshoot or let us know with who we can connect and get advise.
Thanks!!

[simran-concret]

Hi @dmadhwani , @james-wang-sfdc any update here?

[dmadhwani]

hi @simran-concret best way to reachout tosalesforce team is via opening investigation and involving support engineers. So that salesforce engineers can get all needed data, org access. cc: @dineshrohra

[simran-concret]

Hi @dmadhwani we have already opened the case with support team but they were not able to helping out this issue also they are not able to connect with your team to troubleshoot, please let me know I can open a new case and send it over here giving org access, will it work for you as we are stuck here.

[danielkostrzewski-bib]

@simran-concret
Please verify your SF_AUTH_ENDPOINT, it should be sth like this
SF_AUTH_ENDPOINT=https://.my.salesforce.com/services/oauth2/token
so I think in your case
SF_AUTH_ENDPOINT=https://concretio-eb-dev-ed.develop.my.salesforce.com/services/oauth2/token