Support lightening custom domain in SFDC connector
None
Hi Team,
We have a customer who is creating SFDC connector using custom domain as "https://********.lightning.force.com/"
Due to this, we are unable to authorize connector and resulting in "Token null - Authorization failed" issue. As a workaround, we are using "https://*******.my.salesforce.com/" as "custom domain" and it works fine.
Can we please support lightening domain as "https://********.lightning.force.com" while creating SFDC connection ? SS : https://cl.ly/142b4a855042
Best,
Hardik
We have a customer who is creating SFDC connector using custom domain as "https://********.lightning.force.com/"
Due to this, we are unable to authorize connector and resulting in "Token null - Authorization failed" issue. As a workaround, we are using "https://*******.my.salesforce.com/" as "custom domain" and it works fine.
Can we please support lightening domain as "https://********.lightning.force.com" while creating SFDC connection ? SS : https://cl.ly/142b4a855042
Best,
Hardik
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
We will take this enhancement request to the abcklog for prioritization.
Thanks!
Hi@sumesh ,
Do we have ETA to this enhancement request? We have few customers who have noticed similar behaviour when using lightening URL.
We just wasted a few weeks trying to connect our sandboxes going back and forth with our SF admins and turns out the issue was this… :(
we ran into this issue during initial authentication, and needed a call with support to resolve it.
I just ran into this too. Cmon Gainsight can we please fix this? I just lost 30 minutes trying to figure out what was wrong...
Hi@rakesh !
Can you please provide us the tentative ETA for this request? It’s been impacted to multiple customers.
Best,
Hardik
Any updates on this??