Forum Discussion

Miike's avatar
Miike
Brass Contributor
Nov 28, 2024
Solved

Federation Issues - No protocol handlers?

Hi All, It's been a number of years since I've federated a domain with Entra, i'm flipping this back in a home environment to complete some testing. Would appreciate some troubleshooting thoughts. ...
ADFS
Authentication
  • LijuV's avatar
    LijuV
    Dec 09, 2024

    I'm running into the same issue with v2.4.27.0 of Entra Connect. v2.3.8.0 works fine.

Miike's avatar
Miike
Brass Contributor
Nov 30, 2024

Still working on this one, but I’ve noticed that the active endpoint works fine, Teams/OneDrive etc all login as expected. Anything using a passive endpoint fails.

  • LijuV's avatar
    LijuV
    Icon for Microsoft rankMicrosoft
    Dec 09, 2024

    I'm running into the same issue with v2.4.27.0 of Entra Connect. v2.3.8.0 works fine.

    • Manukumar's avatar
      Manukumar
      Copper Contributor
      Jan 31, 2025

      I encountered the same issue with AADC v2.4.27.0, which was resolved after upgrading to v2.4.129.0. After the upgrade, I had to reset the Federation.

    • Miike's avatar
      Miike
      Brass Contributor
      Jan 21, 2025

      LijuV,

      Looks the be fixed in 2.4.129.0 (Released 15/01/25) according to the release notes. I will test this week, but hopefully no more issues.

      Added Features
      Auditing administrator events in Microsoft Entra Connect Sync enabled for logging any admin changes made on Entra Connect Sync. This includes changes made using the UI and the PowerShell scripts. For more information see Auditing administrator events in Microsoft Entra Connect Sync (Public Preview)


      Bug fixes
      Fixed the removal of the SSPR configuration when changes are made on the Azure AD Connector and saved in the Sync Service manager UI
      Fixed validation for the Global Administrator/Hybrid Identity Administrator role done during Entra Connect Sync installation and users with Global Administrator/Hybrid Identity Administrator through Privileged Identity Management (PIM).
      Fixed the "no registered protocol handlers" error on Federate with AD FS scenario.
      Fixed "Relying party must be unique (conflict error)" error on Federate with AD FS scenario.

       

    • Miike's avatar
      Miike
      Brass Contributor
      Dec 10, 2024

      That was it! Thank you so much, I spent hours/days trying to figure out what’s going on. 

      no idea what changed as part of the federation process, even using the legacy msol federation commands couldn’t get the RPT to work. 

      I’ve gone back to v2.3.8.0 and will keep that for testing when needed. Maybe we will see it fixed in the future.

       

       

Resources