Skip to main content

When in my dev hub am trying to link the namespace, then getting the error below. The connected app is disabled by Salesforce; that's why I cannot uncheck the PKCE validation. Tried with tooling api also, did not able to do it. 

 

How to link the namespace? Is there any alternate way? 

 

#Salesforce Developer  #Salesforce Admin

1 resposta
  1. 17 de ago., 18:37

    Hi Souvik - a few things to try first, then the likely reality given what you're seeing. 

     

    Quick things to rule out (these clear most OAuth/PKCE hiccups in the linking flow): 

    1. Do the link in a fresh incognito/private window with no other Salesforce sessions open. A PKCE validation error in a browser OAuth flow is very often a stale/mismatched session - the challenge sent on the authorize step doesn't line up with the verifier on the token step because another logged-in org or old cookies got in the way. A clean session usually clears it. 

    2. Confirm My Domain is deployed (and on the enhanced domain) in the namespace org - namespace orgs without proper My Domain config can hit OAuth errors during linking. 

    3. Make sure you're logging in as a System Administrator in both the Dev Hub and the namespace org during the flow. 

     

    Now the reality: you're right that you can't turn PKCE off here - the connected app behind namespace linking is Salesforce-managed, so its 'Require PKCE' setting is platform-enforced and not something you (or the Tooling API) can change. So if the incognito / My Domain / admin checks don't clear it, this isn't a config you can fix on your end - it has the hallmarks of a platform issue with that managed app. 

     

    In that case: check Salesforce Known Issues for 'namespace linking PKCE', and since this blocks a core packaging workflow (and isn't a free-org limitation), log a Salesforce Support case with your two screenshots and the org IDs - that's the correct path, and Support can act on the managed connected app where you can't. 

     

    If you can paste the exact error text from the screenshot, I can sanity-check whether it's the session mismatch (fixable by you) versus the managed-app enforcement (Support). Hope that helps unblock it!

0/9000