Document item names for saved passwords and OAuth tokens in password managers

[AliveDevil]

With ¹ there is now a non-zero chance, that support is required when an OAuth token is falsely configured (or should be deleted).

This changes the preferred format for Credential Manager entries from "app:Protocol" to "app:OAuthClientId".

Footnotes

1. Save OAuth tokens with port number, scheme and hostname from token URL. cyberduck#15393 ↩

[dkocher]

I don't see this requires documentation as there is a fallback implemented ¹ for the deprecated format.

Footnotes

1. https://github.com/iterate-ch/cyberduck/pull/15393/files#diff-1920b3f5f29d4ad7bfc6e3586784e7fd8356c7e4722264e23ba7ddcad4fa42d2R253 ↩

[AliveDevil]

The fallback doesn’t affect support cases, where users are directed to delete saved credentials for an OAuth Id.

thus support isn’t „delete onedrive“ but „delete 'id'“. The oauth ids used in this scheme should be added to docs, so that support doesn’t have to look them up every time in the default profiles - or users can use that information independently for troubleshooting.

[dkocher]

The fallback doesn’t affect support cases, where users are directed to delete saved credentials for an OAuth Id.

thus support isn’t „delete onedrive“ but „delete 'id'“. The oauth ids used in this scheme should be added to docs, so that support doesn’t have to look them up every time in the default profiles - or users can use that information independently for troubleshooting.

You say we should document in general the naming schemes used to save credentials in the keychain and credentials manager.