SOAP App Password migration – GetEncryptedPassword clarification

We are migrating an existing DocuSign SOAP integration from legacy authentication to App Password authentication and need clarification on one specific scenario.

Our current SOAP authentication flow is:

1. The user enters their DocuSign credential in our application.
2. We authenticate using `credential.asmx`.
3. We call `GetEncryptedPassword()` on `accountmanagement.asmx`.
4. We store the DocuSign-issued encrypted password returned by `GetEncryptedPassword()`.
5. Subsequent SOAP calls (`api.asmx`) authenticate using the `[IntegratorKey]email` username format and that encrypted password through WS-Security / `X-DocuSign-Authentication`.

We have tested replacing the user's regular DocuSign password with an **App Password**. The initial authentication and `GetEncryptedPassword()` call succeed.

We need confirmation on the following two questions:

**1. If `GetEncryptedPassword()` is called after authenticating with an App Password, are subsequent SOAP API calls using the returned encrypted password still classified by DocuSign as Legacy Authentication?**

**2. If YES, should we stop using `GetEncryptedPassword()` and instead send the App Password directly as the password value in the existing SOAP WS-Security / `X-DocuSign-Authentication` authentication mechanism? Would those calls then no longer be classified as Legacy Authentication?**

We are **not asking whether SOAP itself is being deprecated**. We understand that App Password is the supported authentication migration path for SOAP integrations.

We specifically need to determine whether the DocuSign-issued encrypted password returned by `GetEncryptedPassword()` remains compliant after the Basic User Password Authentication retirement.

A YES/NO answer to questions 1 and 2 would be sufficient for us to determine the required remediation.

Thank you.