@ManmohanJangid

you can’t parameterize the Access Token URL field itself. The clean way is to avoid editing it after deploy. Create two auth profiles (e.g., IdP_Test and IdP_Prod) with their own token URLs, then drive which one is used per environment via an Application Setting. Store the profile name (or a flag) in an Application Setting and read it in a small wrapper (DT/activity) to set the auth profile your connector uses. Keep client id/secret in Application Settings too, so secrets stay environment-specific and aren’t moved by deployments. If you need full control, bypass the profile’s token call: build a Token data page that calls the IdP token endpoint where the URL comes from an Application Setting, cache the token, and add the Bearer header on the connector. Manage values through your pipeline (Deployment Manager) so each env supplies its own settings with no manual edits. This keeps test and prod endpoints separate, traceable, and upgrade-safe.