When I press "New connection" on Cyberduck, type my x-goog-project-id and finally press on generated link above I getting text on new Chrome tab (see second-step.png):
<Error>
<Code>MissingSecurityHeader</Code>
<Message>Your request was missing a required header.</Message>
<Details>Authorization</Details>
</Error>
Choose Connect from the connection prompt to connect using Cyberduck instead of the web browser that is not aware of the Google Cloud Storage protocol.
Choose Connect from the connection prompt to connect using Cyberduck instead of the web browser that is not aware of the Google Cloud Storage protocol.
But how I can connect if oauth doesnt work? I haven't "autorization code" and when I click on link above input for get this code, I getting error (second-step.png). If I press "Connect" without autorization code I also getting error "empty key".
Where I can get "autorization code" for creating new connection, if clicking on link above this input thowing error (second-step.png)?
You will only need the x-goog-project-id for the initial connection attempt. Leave the Authorization Code blank until prompted in the next dialog with a title OAuth2 Authentication and the URL to obtain the Authorization Code.
You will only need the x-goog-project-id for the initial connection attempt. Leave the Authorization Code blank until prompted in the next dialog with a title OAuth2 Authentication and the URL to obtain the Authorization Code.
If I leave "Authorization Code" blank, I will get Error Listing directory index "Empty key".
Please workaround this issue by entering the Project Number assigned to your project in the Developers Console. Google has changed the nomenclature and we will have to update our documentation and/or authentication implementation.
Hello.
When I press "New connection" on Cyberduck, type my x-goog-project-id and finally press on generated link above I getting text on new Chrome tab (see second-step.png):
and nothing happens.
Attachments
first-step.png
(11.6 KiB)second-step.png
(22.1 KiB)The text was updated successfully, but these errors were encountered: