fail to push submodules with HTTPS #61670
Unanswered
egoltzman
asked this question in
New to GitHub
Replies: 1 comment
-
Hi, If not i would recommend you to use ssh, since once set up it is a lot easier to use then HTTPS. If you want to check out this doc Hope this helps :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a repo with some AWS submodules and when I try to issue:
![image](https://private-user-images.githubusercontent.com/3929373/255679603-94fea8d5-f84f-424e-ac7a-2181afc46a1e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk5MjcxMjMsIm5iZiI6MTcxOTkyNjgyMywicGF0aCI6Ii8zOTI5MzczLzI1NTY3OTYwMy05NGZlYThkNS1mODRmLTQyNGUtYWM3YS0yMTgxYWZjNDZhMWUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcwMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MDJUMTMyNzAzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YzU1ZDNmYTBiNGVjMjFjYmU4ODYyMzVmYTQ5ODliM2M3OWM0YmYzOTA1ZTA4Njg5MjNiNTY2Yjc3ZDNlOWE4MyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.E_QXE6H7miwIantzJp4Kv-4DFEopERDeqY09doYLc9g)
git push --recurse-submodules=on-demand
I get this:
Pushing submodule 'lib/AWS/Device-Shadow-for-AWS-IoT-embedded-sdk'
Here I get a popup window:
And I select "Sign in with a code", I get the code and visit the URL it point me to and I issue the device activation successfully and press the "Authorize git-ecosystem" button, I get "Congratulations, you're all set!" and then this:
remote: Permission to aws/Device-Shadow-for-AWS-IoT-embedded-sdk.git denied to XYZ.
fatal: unable to access 'https://github.com/aws/Device-Shadow-for-AWS-IoT-embedded-sdk.git/': The requested URL returned error: 403
Unable to push submodule 'lib/AWS/Device-Shadow-for-AWS-IoT-embedded-sdk'
How can I resolve this?
I follow some suggestions I saw to remove the current credentials from Windows credential manager as well as use GitHUB CLI to set the HTTP authentication login, I did those with no change in the above behavior.
Beta Was this translation helpful? Give feedback.
All reactions