A product rename does not, by itself, require a Salesforce integration change. First obtain the vendor’s migration notice and compare the old and new API hostname and path, OAuth authorization and token endpoints, redirect URI, scopes, API version, authentication method, and retirement dates. Change only the Salesforce setting that actually changed, then validate authorization and representative callouts in a non-production environment before touching production.
The safest pattern is to keep vendor-specific values centralized in Named Credentials or the relevant OAuth application. That limits a hostname change to configuration rather than forcing edits throughout Apex, while a callback-URL change, credential rotation, or app migration requires a different procedure.
As an Amazon Associate I earn from qualifying purchases.
What a connected-product rename can—and cannot—change
Marketing names and technical identifiers are separate. A vendor may change its logo, product label, or legal name while leaving every API hostname, resource path, OAuth client, scope, and credential unchanged. Conversely, a rebrand may accompany a new domain, a new API gateway, a new OAuth issuer, or a mandatory API-version upgrade. Salesforce cannot infer which case applies from the new name.
Free tools Windows power users keep installed
One-click scans. No signup required.
Request a written migration notice from the vendor. Record the old and new values side by side, including the date each old value will stop working. Do not construct a replacement URL from the new brand name or rotate credentials merely because the display name changed.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
| Value to compare | Why it matters in Salesforce | Change only when |
|---|---|---|
| API base hostname and path | Determines where callouts are sent | The vendor documents a new host, path, gateway, or resource prefix |
| OAuth authorization endpoint | Where users or an authorization flow grant access | The issuer or authorization server changes |
| OAuth token endpoint | Where access and refresh tokens are exchanged | The vendor moves token service or changes its issuer |
| Redirect or callback URI | Salesforce checks this value during OAuth authorization | The vendor sends a different redirect URI |
| Scopes | Define the permissions granted to the integration | The vendor changes required permissions or scope names |
| API version | Controls request and response behavior | The vendor deprecates the current version or requires a new one |
| Authentication method and credentials | Controls how Salesforce proves its identity | The vendor requires a new client, secret, certificate, signing key, or flow |
| Sunset date | Sets the deadline for migration and rollback planning | The vendor announces a retirement or grace period |
For Salesforce-hosted authorization, use the endpoint appropriate to the environment. Production commonly uses login.salesforce.com; sandboxes use test.salesforce.com or a sandbox My Domain URL. Other supported flows can use a My Domain, Experience Cloud, or custom URL. OAuth endpoints must use HTTPS. Salesforce documents the endpoint patterns in its OAuth endpoint reference.
Map every place the integration is configured
Before editing anything, create an inventory for each Salesforce org and each middleware environment. Include production, every sandbox, scratch or developer org used for testing, and any vendor-managed tenant. A rename project often fails because one old URL remains in a package setting or an integration server even after the obvious Salesforce record is updated.
Named Credentials and External Credentials
A current Named Credential stores the callout URL and authentication parameters separately from the code that invokes it. Apex, External Services, and external data sources can reference that name. Salesforce explains the benefit this way: “For example, if an endpoint URL changes, you update only the named credential instead of updating your Apex code.” See What are Named Credentials?
Inspect both the Named Credential and its associated External Credential or principal. Note the endpoint, authentication protocol, custom headers, certificate, permission assignments, and which users or permission sets can use the principal. Salesforce recommends the newer Named Credential framework introduced in Winter ’23; legacy Named Credentials are deprecated and are no longer enhanced.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Apex and declarative callouts
Search Apex classes, queueables, batch jobs, and invocable actions for hard-coded hostnames, URL fragments, or custom metadata that supplies an endpoint. Review Flow HTTP callouts, External Services, external data sources, and any package-specific integration settings. A code reference such as callout:Vendor_API normally points to a Named Credential; a literal https:// URL requires a code or metadata change when the host changes.
OAuth applications
List connected apps, External Client Apps, client IDs, callback URLs, scopes, policies, certificates, and permitted users. Check whether a callback is stored in one app while the client credentials are stored in another system. A callback change and an API-base-URL change are independent events; one can change without the other.
Remote Site Settings and package configuration
Remote Site Settings still matter when code calls an endpoint without a Named Credential. They do not replace OAuth configuration and do not update a hard-coded URL. Also inspect installed-package custom settings, custom metadata, protected configuration, and post-install records.
Middleware and vendor-managed settings
Integration platforms, scheduled workers, secrets stores, API gateways, and the vendor’s own administration console may each hold a hostname, issuer, client secret, or callback. Record ownership for every value so the Salesforce administrator does not assume that changing a Salesforce record changes the whole integration.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
If the API hostname or path changed
Change the smallest shared configuration that all consumers use. If Apex and declarative features reference one Named Credential, update that credential rather than editing every consumer. Confirm the vendor’s exact new scheme, host, path, TLS requirements, authentication method, and API version before saving.
Update a current Named Credential
- In Setup, open Named Credentials and identify the credential used by the integration. Open the associated External Credential and principal as well.
- Compare the current endpoint with the vendor’s migration notice. Replace only the documented URL, path, or authentication setting. Preserve unrelated headers, permission assignments, and certificates unless the vendor says they must change.
- Save the credential, then check that the principal remains enabled for the integration user, permission set, or permission-set group.
- Run a controlled callout from a sandbox or other non-production org. Verify DNS resolution, TLS negotiation, the expected HTTP status, and a representative resource—not just a connectivity check.
- If the vendor changed scopes or the client, complete a fresh authorization and test token renewal. If the vendor did not change those values, do not rotate them just because the product name changed.
When a credential is shared, document the consumers before changing it. A single update can affect Flows, scheduled jobs, data synchronization, and external data sources simultaneously.
When the URL is hard-coded
Replace the URL in the smallest maintainable layer: custom metadata or a setting first, then the integration class if no configuration layer exists. Update Remote Site Settings when required by that callout architecture, but remember that a Remote Site entry is only an allow-list record; it does not change the URL or OAuth issuer. Deploy the change through the same source-control and validation process used for other Apex or metadata changes.
Recommended Free Tools
If Salesforce’s own My Domain or site URL changed
This is a different failure mode from a vendor rebrand. Salesforce states: “When your My Domain login URL or site login URL changes, named credentials that use that URL stop working.” Follow Salesforce’s documented procedure in Update Named Credentials After a My Domain Change:
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
- Identify Named Credentials containing the old Salesforce login or site URL.
- Replace the old URL with the new Salesforce URL and save each affected credential.
- Trigger a callout using each credential and watch for an authentication prompt or failure.
- Reauthenticate when Salesforce requests it, then repeat the callout and verify the returned resource.
If Salesforce acts as the identity provider, also validate the new URL’s /.well-known/auth-configuration, coordinate any changed OAuth endpoints or JWT audience with relying parties, and verify the login method after the service provider updates its configuration. Salesforce describes that process in Service-provider endpoint update guidance.
If the OAuth callback or redirect URI changed
A connected app’s callback URL is the OAuth redirect URI. At runtime, Salesforce compares the callback supplied by the authorization request with the values saved in the app; it must match a configured value. A mismatch commonly produces an OAuth redirect or callback error even when the API host and client secret are correct.
- Obtain the exact new redirect URI from the vendor, including scheme, hostname, path, port where applicable, and trailing slash behavior.
- Confirm whether production and sandbox use different callback URLs. Treat each as a separate value and test in the correct org.
- In Setup, open the relevant connected app or External Client App, edit its OAuth settings, and add or replace the callback value. Keep the old value temporarily only if the vendor supports a controlled overlap and your security policy permits it.
- Save the app, then start a fresh authorization rather than relying on an existing browser session. Approve the requested scopes and confirm that the authorization code returns to the exact URI.
- Complete the token exchange and run a representative API call. Test refresh-token behavior separately when the integration uses refresh tokens.
Callback URLs used by flows that pass access tokens must use HTTPS or a custom URI scheme. Coordinate the value with the vendor before changing it; a callback update does not prove that the consumer key, secret, scopes, or token endpoint changed. Salesforce’s setup and reconfiguration guidance is available at OAuth setup guidance and connected app reconfiguration.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsShould the connected app become an External Client App?
Product renames do not automatically require an app migration. However, Salesforce says connected-app creation is restricted as of Spring ’26 and recommends External Client Apps for new integrations. Existing connected apps can continue to be used for now, so separate a vendor rename from this platform-policy decision.
Use the migration interface when the existing app is eligible and its OAuth flow is supported. Salesforce says an eligible migration preserves the consumer key and secret, and refresh tokens remain valid. The migration is performed in the Salesforce UI; the original connected app becomes read-only. Do not delete the original app.
| Decision | When it fits | Credentials and operational effect |
|---|---|---|
| Migrate an eligible connected app | The app has no migration-blocking feature and uses a supported flow | Salesforce says the consumer key, secret, and refresh tokens are preserved; plan a validation window |
| Create a new External Client App | The app is ineligible or uses a feature the migration cannot carry over | Create equivalent settings, issue new consumer credentials, update the integration, and plan reauthorization or token replacement |
| Keep the existing connected app temporarily | The rename changed no technical value and migration is not yet required | Continue operating it while tracking Salesforce’s support roadmap and a future migration |
Check migration blockers before clicking Migrate
- User Provisioning
- A custom Apex handler
- Canvas
- Dynamic Client Registration
- Certain SAML encryption configurations
- Some notification subscriptions
- The username-password OAuth flow, which External Client Apps do not support
Salesforce warns that the migration process does not detect use of the username-password flow. Verify the actual flow in code, middleware, and vendor documentation rather than relying only on the migration screen. Review the full eligibility rules and procedure in Migration eligibility and procedure.
Salesforce’s identity and access documentation says connected apps are planned to lose support in Summer ’27: they may continue working, but Salesforce will no longer fix bugs or support their integrations and authorization flows. This is a roadmap item, not proof that a current rename requires immediate migration. Recheck the current release documentation before scheduling work; the relevant page is Salesforce identity and access release documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Validate safely before production cutover
Use a sandbox or another non-production endpoint whenever the vendor provides one. If the vendor has no sandbox, use a restricted test account, a read-only operation, or a maintenance window with a rollback plan.
- Confirm target mapping. Verify that the Salesforce sandbox points to the vendor’s test host and production points to the production host. Check that no test credential can reach production data.
- Check authorization metadata. Confirm the authorization endpoint, token endpoint, client ID, secret or certificate, callback URI, scopes, audience, and permitted users.
- Authorize from a clean session. Test a new authorization in a private browser session or with revoked test tokens. This exposes callback and consent problems that an existing token can hide.
- Test a normal callout. Exercise a representative read and, in a safe test record, a write if the integration performs writes. Confirm response parsing, API version behavior, and resource paths.
- Test renewal. If refresh tokens are used, allow or force access-token expiry and verify that the integration obtains a new token without user intervention.
- Inspect logs. Correlate Salesforce debug logs, integration-worker logs, and vendor request IDs. Remove access tokens and secrets from any ticket or shared log.
- Run a parallel observation period. Monitor scheduled jobs, queue depth, error rates, and data reconciliation for at least one normal processing cycle before declaring success.
- Communicate user impact. Tell users whether a one-time consent or reauthentication prompt is expected and provide the exact support path.
Diagnose common failures
| Symptom | Likely cause | Action |
|---|---|---|
| DNS error or connection timeout | Old hostname, blocked egress, or incorrect environment | Compare the host character-for-character with the vendor notice; check network allow-lists and sandbox-versus-production mapping |
| TLS or certificate failure | New host has different certificate requirements or an outdated trust configuration | Use the vendor’s documented TLS requirements; do not disable certificate validation |
| Redirect URI mismatch | Runtime callback differs by scheme, path, port, or slash | Copy the exact URI into the app configuration and start a fresh authorization |
invalid_client or unauthorized client |
Wrong client, secret, certificate, or app policy | Verify which app owns the credentials and whether the vendor issued replacements; rotate only through the documented process |
| Invalid or insufficient scope | Scope names or consent changed | Compare requested and granted scopes, update the app and vendor configuration, then reauthorize |
| 401 after a successful token exchange | Wrong audience, API host, token type, or expired token | Check issuer and audience, use the access token for the documented host, and test refresh behavior |
| 404 or resource-path errors | API version or path changed while the base host appears correct | Compare the complete path and version, not just the hostname; update the shared configuration or code layer that owns it |
| Calls work manually but scheduled jobs fail | Different integration user, permission set, principal, or environment variable | Run the job identity through the same Named Credential and inspect its permissions and secret assignment |
| Every callout fails after a Salesforce URL change | Named Credentials still contain the former My Domain or site URL | Update affected credentials, trigger a callout, and reauthenticate as Salesforce instructs |
Security, rollback, and change control
- Keep old and new endpoint values, app IDs, scope lists, and sunset dates in the change record, but never store secrets in plain text.
- Use least-privilege scopes and a dedicated integration user. Do not grant broader permissions simply to make a migration pass.
- Prefer an additive callback change and a short overlap only when the vendor explicitly supports it; remove the old callback after cutover.
- Back up metadata and record the pre-change Named Credential, External Credential, app policy, and package settings so rollback is precise.
- Define rollback triggers before deployment: repeated authorization failures, data-integrity discrepancies, elevated 4xx/5xx responses, or a vendor-side outage.
- For a new External Client App, preserve the original connected app while validating the replacement. Salesforce cautions against deleting the original app after migration.
- After the old endpoint’s sunset, remove obsolete secrets, callbacks, Remote Site Settings, and firewall allow-list entries according to your retention policy.
A practical decision sequence
- Name only: If the vendor confirms that host, OAuth endpoints, callback, scopes, credentials, and API version are unchanged, update labels and documentation only. Do not mass-rename Salesforce metadata.
- Host or path changed: Update the shared Named Credential or the configuration layer that owns the URL, then test representative callouts and token renewal.
- Callback changed: Update the exact OAuth redirect value in the app and vendor console, then perform a fresh authorization.
- Credentials or scopes changed: Follow the vendor’s rotation and consent procedure, update the External Credential or app policy, and plan any user reauthorization.
- Salesforce My Domain changed: Find Named Credentials containing the old Salesforce URL, replace it, trigger a callout, and reauthenticate if prompted.
- App policy requires modernization: Check External Client App eligibility and flow compatibility. Migrate an eligible app or create a new one with equivalent settings, preserving the old app during validation.
The principle is simple: trace the vendor’s documented technical change to the Salesforce field that represents it. A display-name change alone is not a technical change, while a hostname, issuer, callback, scope, credential, or platform-policy change deserves its own controlled update and test.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
