How to run the Salesforce SOAP login inventory board

Use this when you must list integrations that still call SOAP login() across orgs before 2026-12-01, when Use Any API Auth becomes required. The board is read-only and local. Re-check Salesforce Help and secondary calendars before closing security tickets.

1. Step 1. Confirm the December 1 2026 Use Any API Auth requirement for SOAP login() on official Help / Release Update materials.
2. Step 2. Per org, pull Login History and API Total Usage for SOAP login callers. Note users and connected systems.
3. Step 3. Grep codebases and middleware for Partner/Enterprise WSDL login() usage.
4. Step 4. Ask ISV and middleware vendors whether they still authenticate with SOAP login.
5. Step 5. Open the home board and add a row per hit: org, evidence source, Use Any API Auth yes/no, recent login, owner, IP breadth note.
6. Step 6. Decide path per row: deliberately assign Use Any API Auth, or migrate to External Client App + OAuth (client credentials / JWT Bearer).
7. Step 7. Note adjacent rules: broad IP ranges needing security tokens; six-month unused login disable; sandbox vs production dates on the security timeline.
8. Step 8. Copy Markdown into the security ticket; assign owners; verify dates on Help and The Daily Org—never treat this static board as authoritative alone.

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates.