locked
CRM 2011 SDK - "The authentication endpoint Username was not found on the configured Secure Token Service" RRS feed

  • Question

  • I'm trying to connect to CRM Explorer in Visual Studio 2010 CRM 2011 SDK.  My configuration is Windows Server 2008 R2, with CRM 2011 Rollup 16.  We are using Claims Based Authentication through PingFederate, and have IFD.

    When I try to connect, I get the error: "The authentication endpoint Username was not found on the configured Secure Token Service"

    We do not use the e-mail router.  I turned on tracing and don't see anything on the server side that indicates any errors.  Any ideas?


    Susan

    Thursday, March 27, 2014 2:14 AM

All replies

  • If you're using PingFederate, rather than MS ADFS, then it will be very difficult to diagnose the problem, as there is very little information about using PingFederate with Claims Authentication (or, I've not found anything useful).

    Does CRM work correctly for users, and can you access CRM programmatically using the CRM SDK assemblies ? If so, I suggest you live with that, and don't spend time trying to get additional tools like the CRM Explorer to work


    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Thursday, March 27, 2014 8:16 PM
    Moderator
  • Just to add, logging in from the browser works with no issue and not does the outlook plugin.  I can also access CRM from the SSIS plugin we purchase from Kingswaysoft.  CRM Explorer in the SDK is the only place we are having this issue.

    Here is what the trace log looks like:

    [2014-03-27 16:39:39.253] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   72 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Verbose |ReqId: 3f25aa20-c35c-4042-9456-102a48442b92 | AuthenticationEngine.Execute  ilOffset = 0xA1
    >AUTH: Request [GET https://dynamics.crm.com/XRMServices/2011/Discovery.svc?wsdl] from [192.168.100.39] entered Authentication Pipeline.
    [2014-03-27 16:39:39.253] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   72 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Verbose |ReqId: 3f25aa20-c35c-4042-9456-102a48442b92 | AuthenticationPipeline.Authenticate  ilOffset = 0x11
    >AUTH: AuthenticationProvider [Microsoft.Crm.Authentication.PassThroughAuthenticationProvider] will be attempted.
    [2014-03-27 16:39:39.253] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   72 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Info |ReqId: 3f25aa20-c35c-4042-9456-102a48442b92 | AuthenticationPipeline.Authenticate  ilOffset = 0x11
    >AUTH: AuthenticationProvider [Microsoft.Crm.Authentication.PassThroughAuthenticationProvider] handled request [https://dynamics.crm.com/XRMServices/2011/Discovery.svc?wsdl] from [192.168.100.39].
    [2014-03-27 16:39:39.253] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   71 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Verbose |ReqId: d54ff6b0-c8a4-4ca1-9c40-8e8f3e0593e0 | AuthenticationEngine.Execute  ilOffset = 0xA1
    >AUTH: Request [GET https://dynamics.crm.com/XRMServices/2011/Discovery.svc?wsdl=wsdl1] from [192.168.100.39] entered Authentication Pipeline.
    [2014-03-27 16:39:39.253] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   71 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Verbose |ReqId: d54ff6b0-c8a4-4ca1-9c40-8e8f3e0593e0 | AuthenticationPipeline.Authenticate  ilOffset = 0x11
    >AUTH: AuthenticationProvider [Microsoft.Crm.Authentication.PassThroughAuthenticationProvider] will be attempted.
    [2014-03-27 16:39:39.253] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   71 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Info |ReqId: d54ff6b0-c8a4-4ca1-9c40-8e8f3e0593e0 | AuthenticationPipeline.Authenticate  ilOffset = 0x11
    >AUTH: AuthenticationProvider [Microsoft.Crm.Authentication.PassThroughAuthenticationProvider] handled request [https://dynamics.crm.com/XRMServices/2011/Discovery.svc?wsdl=wsdl1] from [192.168.100.39].
    [2014-03-27 16:39:39.253] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:  117 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Verbose |ReqId: 777659e4-52fc-4499-ab4e-0a062ddf058a | AuthenticationEngine.Execute  ilOffset = 0xA1
    >AUTH: Request [GET https://dynamics.crm.com/XRMServices/2011/Discovery.svc?wsdl=wsdl0] from [192.168.100.39] entered Authentication Pipeline.
    [2014-03-27 16:39:39.253] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:  117 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Verbose |ReqId: 777659e4-52fc-4499-ab4e-0a062ddf058a | AuthenticationPipeline.Authenticate  ilOffset = 0x11
    >AUTH: AuthenticationProvider [Microsoft.Crm.Authentication.PassThroughAuthenticationProvider] will be attempted.
    [2014-03-27 16:39:39.253] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:  117 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Info |ReqId: 777659e4-52fc-4499-ab4e-0a062ddf058a | AuthenticationPipeline.Authenticate  ilOffset = 0x11
    >AUTH: AuthenticationProvider [Microsoft.Crm.Authentication.PassThroughAuthenticationProvider] handled request [https://dynamics.crm.com/XRMServices/2011/Discovery.svc?wsdl=wsdl0] from [192.168.100.39].


    Susan

    Thursday, March 27, 2014 8:46 PM
  • We are setting up Ping Federate for SSO for Dynamics CRM as well. And we also have KingswaySoft's CRM connector. I am a little concerned on authentication from the CRM connector via Ping. Do you use an AD as the IDP in Ping? Our users will be using Google ID.

    Thanks in advance.

    Thursday, October 16, 2014 2:57 AM
  • Hi guys, late to the party. 

    When using a third-party federation service, please make sure to supply a Home Realm Uri (it is located in the Advanced Settings tab). Please feel free to reach out to us through our official support channel if this continues to be an issue. 

    Cheers,


    Daniel Cai | http://danielcai.blogspot.com | @danielcai | Data Integration made easy with SSIS Integration Toolkit

    Monday, November 17, 2014 5:12 PM