Skip to main content
Question

IdP Testing Configuration Error

  • Oct 28, 2026 9:24 PM UTC
  • 1 reply
  • 5 views
Forum|alt.badge.img+6

I have built the Jamf Connect profiles with Jamf Connect Configurator, saved them out and they work flawlessly when I manually install them on a Mac, but I cannot seem to get them set up properly in Jamf Pro.

I was unable to upload them via the direct JCC upload function, so I saved them as .mobileconfig. However, when I upload them in Configuration Profiles, they are blank. Now I am trying to replicate the settings manually but keep getting the error message “IdP Testing Configuration Error: The Selected Identity provider (IdP) field is empty or the value is not supported. Testing is available for the following IdPs: Okta and Azure.” when I try to use the “Test SSO” button inside the payload section of COnfiguration Profiles.

I don’t see an Azure option, only EntraID. Does the Test SSO button not work or am I missing something? EntraID SSO is setup and works for all our apps (Jamf Accounts, Jamf Pro and Jamf Protect). 

I am working (struggling) to deploy the configuration profiles, and any help would be greatly appreciated.

 

Thanks,

Matt

1 reply

justin_smith
Forum|alt.badge.img+8
  • justin_smith
  • New Contributor
  • Oct 28, 2026 9:36 PM UTC

The blank profiles and the IdP error are the same problem: the settings aren't reaching Jamf Pro as a native Jamf Connect payload.

 

A .mobileconfig exported from Jamf Connect Configuration and uploaded as a regular configuration profile displays blank in Jamf Pro when it's signed — Jamf Pro can't render or edit a signed upload; it just deploys as-is. If you need to view or edit the payload in the GUI, re-export it unsigned. That's what pushes you into recreating the settings by hand, and the hand-built copy is where the error comes from: "IdP Testing Configuration Error" means the OIDCProvider value is empty or isn't one of the exact strings Jamf Connect accepts. Typed-in names like "Entra ID" or "Microsoft" won't pass. For Jamf Connect Login the supported values are Azure, GoogleID, IBMCI, OneLogin, and PingFederate, and Okta has its own selection in the Configuration app. The value has to come from the Identity Provider pop-up, not be typed in.

 

What works reliably:

 

1. Build the configuration in Jamf Connect Configuration and test it there first (Test, then OIDC — and ROPG too if you use it). That test runs the same validation that's failing for you now.

2. When saving, use the built-in Jamf Pro upload — the Jamf Pro Upload checkbox plus Check Connection, in .mobileconfig format — instead of uploading the file manually under Configuration Profiles. Jamf's documentation calls this out as the required path for Jamf Pro, and it lands the payload intact.

3. If you'd rather build it in Jamf Pro directly, use the dedicated Jamf Connect payload in the profile editor and pick your IdP from the pop-up so OIDCProvider gets a supported value.

 

One side note if your IdP is Google: there's a known Jamf Connect Configuration issue (PI-007810) where selecting GoogleID drops some required keys. The workaround is to enter a redirect URI under Advanced OIDC in the OIDC Redirect URI field.

 

Hope that gets you unstuck.

Terms & ConditionsAccessibility statement