Bug 1299870

Summary:	[GSS] (6.2.z) Business Central Repo Clone Fails To Clone SCP Style SSH URLs
Product:	[Retired] JBoss BRMS Platform 6	Reporter:	Alessandro Lazarotti <alazarot>
Component:	Business Central	Assignee:	manstis
Status:	CLOSED EOL	QA Contact:	Jiri Locker <jlocker>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.2.0	CC:	alazarot, kverlaen, lpetrovi, tdavid
Target Milestone:	CR1
Target Release:	6.2.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1299619	Environment:
Last Closed:	2020-03-27 20:03:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1299619
Bug Blocks:	1309326, 1309327

Description Alessandro Lazarotti 2016-01-19 12:57:56 UTC

+++ This bug was initially created as a clone of Bug #1299619 +++

Description of problem:

Git supports two styles of URI's for SSH protocol. Business Central fails with "invalid URL format" when using the SCP style for SSH. This problematic because github by default uses the SCP style for SSH and does not seem to support the SSH style URL anymore.


Version-Release number of selected component (if applicable):
6.2.0 GA

How reproducible:
Everytime 

Steps to Reproduce:
1) Go to the admin tab
2) Click repositories->Clone Repository
3) Fill out the form using any ssh URL protocol provided by the github UI. I used git:sherl0cks/TestKnowledgeRepo.git

Actual results:
See screenshot. Error with "invalid URL format"

Expected results:
It clones the repo just like https URLs.


Additional info:

--- Additional comment from JBoss Product and Program Management on 2016-01-18 14:00:07 EST ---

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 2 Kris Verlaenen 2016-02-23 13:31:39 UTC

See discussion in linked BZ, keys without passphrase can be supported by relaxing the url validation and should work.

Comment 9 Jan Hrcek 2016-03-07 09:23:10 UTC

Verified manually with 6.2.2 patch (setting org.uberfire.nio.git.ssh.passphrase property & cloning the repo mentioned in the description) and it's working fine.