Adobe Sign REST API OAuth Login Redirecting to User Account Page Instead of Returning Auth Token

Description:

We’ve integrated Adobe Sign into our application using the available REST APIs and OAuth 2.0 for authentication. While the integration mostly works, we’re encountering an issue with the login behavior during the OAuth flow.

Issue Details:

When the Adobe Sign login dialog opens (triggered via the OAuth authorization URL), the user is presented with the standard login screen. However, upon clicking "Sign In" on the first screen:

• Instead of returning the authorization code or access token and redirecting back to the requesting app's redirect URI (as expected in OAuth 2.0 flow),

• The user is taken to their Adobe account page (https://secure.adobesign.com/public/login), and the dialog remains open.

This breaks the intended OAuth flow. Ideally, once authentication is successful:

• The login dialog should close, and

• The requesting application should receive the authorization code/token via the redirect URI.

Expected Behavior:

• After successful login, Adobe should redirect to the configured redirect_uri with the authorization code or token (as per the response_type).

• The popup/dialog should close, and the calling application should regain control with the token to proceed.

Current (Incorrect) Behavior:

• Adobe Sign redirects to the user’s account page instead of back to our app with the auth response.

Request:
Could you please confirm if this is a known issue or if there’s a specific configuration required to ensure proper OAuth flow behavior for embedded Adobe Sign integration? Any advice or workaround would be appreciated.