Solved

CRM Connection using SDA

  • 2 April 2020
  • 2 replies
  • 163 views

Hi All,

 

I have an SDA connection into our network and i'm attempting to access the CRM. I am able to telnet to the CRM server and the actual connection is working but I am now getting an error message of "The authentication endpoint Username was not found on the configured Secure Token Service." I've searched the web for information and I am not getting much help for the articles. My crm version is 20*personal details removed*.1.1.1005. Can anyone provide some direction on making the connection given the specific error?

 

Thanks,

Ben

icon

Best answer by bhickok2 13 April 2020, 13:49

It turns out that if you are using adfs on a on prem server there is a port issue where the sda is trying to communicate over 443 for both the crm and the adfs. With the help of the dev ops team we found out the connection as not possible. Thank for the attempts to help!

View original

2 replies

Hello  @bhickok2 ,


 


Please kindly review the threads below:


 


Troubleshooting Claims-Based Authentication Errors:


https://help.k2.com/kb002030


 


 


Authentication and Authorization in K2:


https://help.k2.com/kb002026


 



The authentication endpoint Username was not found on the configured Secure Token Service:


https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/223369/the-authentication-endpoint-username-was-not-found-on-the-configured-secure-token-service


 


 


Fix for: 'The Authentication Endpoint Username Was Not Found':


https://kb.omni-ts.com/entry/1208/


 


 


"The authentication endpoint Username was not found on the configured Secure Token Service" Error When Registering:


https://support.clickdimensions.com/hc/en-us/articles/115001157433--The-authentication-endpoint-Username-was-not-found-on-the-configured-Secure-Token-Service-Error-When-Registering


 


Hope this helps.

It turns out that if you are using adfs on a on prem server there is a port issue where the sda is trying to communicate over 443 for both the crm and the adfs. With the help of the dev ops team we found out the connection as not possible. Thank for the attempts to help!

Reply