Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-4609

[GSS] (6.4.z) Not able to clone BPMS server git repository over ssh protocol over WAS server.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 6.4.4
    • 6.4.0
    • Business Central

    • WAS 8.5.5
      Windows

    • Documentation (Ref Guide, User Guide, etc.)
    • CR1
    • Hide
      Updated documentation can be found on community GitHub:

      kiegroup/kie-docs/docs/shared-kie-docs/src/main/asciidoc/Workbench/Installation/Installation-section.adoc
      Show
      Updated documentation can be found on community GitHub: kiegroup/kie-docs/docs/shared-kie-docs/src/main/asciidoc/Workbench/Installation/Installation-section.adoc
    • jBPM sprint 2, jBPM sprint 3

      Customer is using BPMS with WAS 8.5.5 on windows machine. They are not able to clone repository over ssh protocol when LDAP authentication is enabled on WAS ND server for business central. We have tried with org.uberfire.domain=WSLogin and org.uberfire.domain=defaultWIMFileBasedRealm but no luck.

      ~/.ssh/config file look like as:

      Host 10.10.10.10
VerifyHostKeyDNS no
StrictHostKeyChecking no
HostKeyAlgorithms +ssh-dss
ServerAliveCountMax 10
ServerAliveInterval 30

      Debug enabled logging and logging from server side attached.

        1. kie-wb_AllThreads.jpg
          kie-wb_AllThreads.jpg
          222 kB
        2. kie-wb_sshd-SshServer[6dbd42c0]-nio2-thread-4.jpg
          kie-wb_sshd-SshServer[6dbd42c0]-nio2-thread-4.jpg
          159 kB
        3. Logging
          11 kB
        4. RHBPMS-4609.pdf
          269 kB
        5. SystemOut.log
          350 kB

            docmrc97 Mark Coble (Inactive)
            rhn-support-abhumbe Abhijit Humbe
            Bojan Sremac Bojan Sremac (Inactive)
            Mark Coble Mark Coble (Inactive)
            Bojan Sremac Bojan Sremac (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: