Authentication Upgrade

v3.0.0 Authentication Upgrade

To upgrade to Flow Scanner v3.0.0, you must follow the new post-installation instructions provided below after uninstalling any previous versions. This release introduces a new package name and namespace, requiring a clean setup to ensure compatibility and avoid conflicts.

Authentication Upgrade

• Replaced Visualforce page and token-based authentication with a Connected App using JWT Bearer Flow for server-to-server Tooling API access.
• Leverages a self-signed certificate (Flow_Scanner) and Consumer Key stored in Custom Metadata (Flow_Scanner_OAuth_Config__mdt).
• New Apex class ToolingAPI handles JWT generation, token caching, and Tooling API queries with enhanced error handling.

Post-Installation Setup

• Manual Connected App creation required due to Salesforce 2GP packaging limitations (ghost metadata errors prevented reliable packaging).
• Steps include:
  • Creating a Connected App (Flow_Scanner_JWT) with specific OAuth settings (scopes: api, refresh_token, offline_access).
  • Generating and uploading a self-signed certificate (Flow_Scanner).
  • Copying the Consumer Key to Custom Metadata.
  • Pre-authorizing via Profiles (optional) and assigning the Flow Scanner User permission set.
• Process takes ~3–5 minutes; detailed instructions provided in README.

New Package Name and Namespace

• Package name changed to flow-scanner (ID: 0HogK0000000ZFVSA2) to avoid conflicts with prior lightning-flow-scanner installations.
• Namespace changed to lfscanner for the same reason.
• Recommendation: Uninstall previous versions before installing v3.0.0 to prevent namespace or metadata conflicts.