Discover the winners & finalists of the 2022 Dataiku Frontrunner Awards!READ THEIR USE CASES

notebook import from git with LDAP credentials

clayms
Level 3
notebook import from git with LDAP credentials

We log into Dataiku and our GitHub enterprise server with the same LDAP (Microsoft Active Directory) credentials.  However, when I want import a notebook from our gitHub server, I get the following error:

 

Branches and tags could not be fetched from remote Git, caused by: 
IOException: Process failure, caused by: IOException: 
Process execution failed (return code 128) 
(error=Host key verification failed. fatal: 
Could not read from remote repository. 
Please make sure you have the correct access rights 
and the repository exists. )

 

I have no problems cloning this repo with either https or ssh links. 
I am aware of this Doc https://doc.dataiku.com/dss/latest/collaboration/git.html#working-with-remotes

However, we are using an Enterprise installation of Dataiku.  Does each user have to ssh into the Dataiku Design Node and create ssh public/private keys, and put the public key in their user settings on gitHub?   By default, Dataiku Design Node users do not have ssh access to the Design Node.  Should they run a notebook in a local dss (not containerized) code environment and use `%%bash` shell cell magic to run the ssh-keygen commands and get the public key that way.  Or should there be one key for the "dataiku" user?

Is there a way to get Dataiku to use the same LDAP credentials?

Operating system used: centos

Operating system used: centos
0 Kudos
1 Reply
AlexT
Dataiker

Hi @clayms ,

Interactions with the remote repositories are always performed by the DSS system user, including fetching notebooks. 

To fix the current error you have "Host key verification failed".

Connect via SSH as the DSS system user and update ~/.ssh/known_hosts.  by running :
for example( if you use github)  : ssh -T git@github.com     

Als explained here:  https://doc.dataiku.com/dss/latest/collaboration/git.html#troubleshooting

You can also define separate SSH keys per group( but not per user) as explained here which would be used to push to remote repositories:

https://doc.dataiku.com/dss/latest/collaboration/git.html#example-2-use-a-ssh-key-per-group 

The core.sshCommand requires git version 2.10+ to be installed on DSS. 

Individual commits ( not pushes) will still be attributed to the individual users without them having ssh keys. 

Hope that helps!

0 Kudos