---
schema_version: "1"
id: 183d25ff052057ee361513a1863ffea7794f1254bf60705112f010f8e5a47bd7
title: Build More Secure Integrations with Cross-Org Adapter Support for Named Credentials
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_sf_connect_xorg_named_credentials.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_sf_connect_xorg_named_credentials.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ea4b4bb31dc01f596ece09b64d9262f178e484f7ef9dfae11caab80539ccca9e
description: The Salesforce Connect cross-org adapter now supports named credentials for authentication. The SOAP login() call is being retired, and password authentication, and OAuth 2.0 authentication won't be supported in the future, so we recommend that you migrate any cross-org adapter external data sources to use named credentials, a more robust and secure authentication method.
products:
  - Cross Cloud
release: "262"
---
# Build More Secure Integrations with Cross-Org Adapter Support for Named Credentials

The Salesforce Connect cross-org adapter now supports named credentials for authentication. The SOAP login() call is being retired, and password authentication, and OAuth 2.0 authentication won't be supported in the future, so we recommend that you migrate any cross-org adapter external data sources to use named credentials, a more robust and secure authentication method.

**Where:** This change applies to Lightning Experience and Salesforce Classic (not available in all orgs) in Enterprise, Performance, Unlimited, and Developer editions.

**How:** In the provider org, first create an external client app and get the consumer key and secret. In the subscriber org, create the external credential or external auth identity provider and use the consumer key and secret. Add a named credential that uses the auth provider you created. Then, when you create a cross-org adapter external data source, there’s a new Authentication Method field. For an existing external data source that uses login(), the field value is Legacy. When you create a new external data source or migrate an existing one, select Named Credential. In the Named Credential field, select the named credential to use for authentication.

#### See Also

- [_Salesforce Help_: Create an External Client App](https://help.salesforce.com/s/articleView?id=xcloud.create_a_local_external_client_app.htm&type=5&language=en_US)
- [_Salesforce Help_: Define an External Data Source for Salesforce Connect Cross-Org Adapter](https://help.salesforce.com/s/articleView?id=platform.xorg_add_external_data_source.htm&type=5&language=en_US)
- [_Knowledge Article_: Platform SOAP API login() Retirement](https://help.salesforce.com/s/articleView?id=005132110&type=1&language=en_US)