For the Facebook Marketing source connector, it would be beneficial to allow BOTH

access Token

and

Oauth

for credentials. This is seen in many other connectors, and I'm not sure why it's not included in Airbyte Cloud -- given that it's included in the Open Source https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connectors/source-facebook-marketing/source_facebook_marketing/spec.py

@John Mikkelson can you explain the your use case do you need

access token

method?

Two streams that require this for us: 1. We are trying to move away from Oauth tied to specific user accounts, and manage by way of access tokens we can manage even when a specific user is unavailable. 2. In the new year, we are hoping to move to Meta Work Accounts. We would also prefer access tokens for the above reasons. 3. We currently maintain a custom facebook connector, and don't want to keep maintaining it in the future.