Version control delivers [HTTP 400] (45234) The repository cannot be reached with the provided URL and SSH Information: No detail information available.
search cancel

Version control delivers [HTTP 400] (45234) The repository cannot be reached with the provided URL and SSH Information: No detail information available.

book

Article ID: 255069

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Accessing version control via AWI returns the following exception:

[HTTP 400] (45234) The repository cannot be reached with the provided URL and SSH Information: No detail information available.
Caused by: com.uc4.api.rest.exceptions.BadRequestException: [HTTP 400] (45234) The repository cannot be reached with the provided URL and SSH Information: No detail information available.

The JCP trace (TCP/IP=9, REST=9) shows the following messages:

U00045105 Log on of 'USER/DEPARTMENT' successful.
          STRT CheckRepositoriesResourceDisabledProvider$$Lambda$484/0x00000008007a0440
          EXIT CheckRepositoriesResourceDisabledProvider$$Lambda$484/0x00000008007a0440 TIME: 0ms
          [email protected]:repository/user.git: ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.
          Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.
          
U00045099 The server replied with following status: '400'
          Response-Headers: [Content-Type=application/json]
          Response-Payload:
          {
            "code" : 45234,
            "error" : "The repository cannot be reached with the provided URL and SSH Information",
            "details" : "No detail information available."
          }

Environment

Release : 12.3.x, 21.0.x

Component: AUTOMATION ENGINE

Cause

Configuration.

Resolution

Github improved the security protocol. See also: https://github.blog/2021-09-01-improving-git-protocol-security-github/

The ssh key needs to be created with the following command:

ssh-keygen -m PEM -t ecdsa -b 256 -C <user>