Hi @Suteja Kanuri​ . it seems access_control_list is working fine with 2.1 api and the run_as_username is updated with it but with our airflow platform using 2.0 api we are facing issue and this parameter is ignored. we want to test the git credential solution that you mentioned above. but i see in the configuration you are asking ssh_keys as well as secret ? can it be authenticated by just PAT or we also need ssh keys ?? can we remove the bold part and only provide credential_keys ?

1. git:
2. auth:
3. type: ssh
4. ssh_key: /path/to/ssh/key
5. known_hosts: /path/to/known_hosts/file
6. secret_name: my_secret_scope_name
7. secret_key: my_git_credentials_key