Dreamweaver Live View authentication scope and expired credential handling

Live View and authentication scope

Dreamweaver Live View is a client-side rendering preview (historically WebKit, later Chromium Embedded Framework). It does not enforce least-privilege authentication scopes for server-side operations such as FTP or publishing. Those operations rely on credentials stored in the site management layer (Site > Manage Sites > Servers), separate from the preview context.

Confirmed behavior

• Expired or invalid credentials surface as a failed put operation, an error dialog, or an entry in the Window > Results > FTP Log, rather than triggering automatic re-authentication.
• Re-authentication is manual: the user must re-enter or update the password in the server settings and reconnect. Dreamweaver does not implement token refresh or OAuth-style renewal for classic FTP/SFTP site connections.
• Credential storage depends on the OS credential store or Dreamweaver site definitions; stale passwords persist until explicitly edited.

Likely explanation & version notes

Because Live View runs locally and does not mediate server connections, any least-privilege enforcement comes from the server account configuration (e.g., an FTP user restricted to a docroot), not from Dreamweaver’s preview engine. Behavior has varied across releases, so CC 2025 users should consult the version-specific release notes for any changes to credential prompting.

1. Open Window > Results > FTP Log and attempt a Put to observe the exact error returned when credentials are expired.
2. Edit the server entry under Site > Manage Sites > Servers, re-enter the password, and use the Test button to confirm manual re-authentication restores publishing.
3. Confirm the Dreamweaver version (Help > About / system info) and compare observed prompt behavior against Adobe’s current documentation for that release.

To refine the recommendation, could you confirm the Dreamweaver version in use?