<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008G7V3MSAVOkta Classic EngineOkta Integration NetworkAnswered2024-04-30T09:18:25.000Z2016-05-15T18:23:45.000Z2017-07-26T18:38:19.000Z

JohnN.03536 (Customer) asked a question.

Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:19 AM
Error message in Microsoft Remote Connectivity Analyzer
When I run the SSO connectivity test here: https://testconnectivity.microsoft.com after converting our federation to Okta, from our on prem ADFS, I always receive the error below.  While authentication seems to work, it'd be nice to undertand why I get an error now, when before (on ADFS) we got the all clear.  I don't want to hit a troubleshooting issue with M$ that they say this is causing the issue.  My searches so far haven't turned up any Okta related results.  

 

Error in the "Analyzing the ADFS metadata document for configuration problems." section: 

The Integrated Windows authentication endpoint is missing on the internal metadata document
  • 2 answers
  • 1.62K views
SteveF.54333 likes this.

  • j5v7c (j5v7c)

    Hello John,

     

    Thanks for posting in the Okta Community!

     

    Have you already verified that the endpoint has been declared in the metadata document prooerly? It may just need to be entered so that the configuration knows where to look.

     

    I think your issue would be best resolved if you submitted a support ticket so that a technician can take a look at your org and see if there is an issue with our end.Starting there would prevent you from having to engage MS for troublshooting.

     

    Please let me know if you have any other comments or questions.

     

    Regards,

    Drew Pador

    Technical Support Engineer

    0EMF00000009YCF
    Expand Post

  • JohnN.03536 (Customer)

    To the best of my understanding the declaration of the endpoint is up to Okta.  the ADFS metadata information is coming from https://<ourdomain>.okta.com/app/office365/<guid>/sso/wsfed/mex.  We have no control over what's being served at this web address.  

     

    I believe I did have a service ticket opened at one point (on a related issue) in which the technician stated that this was occuring because the testconnectivity tool is looking for strictkly ADFS responses.
    Expand Post
This question is closed.
Loading
Error message in Microsoft Remote Connectivity Analyzer