Hi,
Glad to hear you are finding the NiFi Registry features useful. Regarding your question, the “Remote Access User” and “Remote Access Password” properties are only used when the remote URL is an HTTPS url. When it is an SSH url, it is expected that password-less SSH has been configured on your NiFi Registry instance, and the user/password properties are ignored. If it is possible, I would suggest you try one of the following: 1. Setup password-less SSH (e.g., if you can ensure no one else has access to the private ssh key through some other mechanism, such as file permissions) 2. If your remote bitbucket accepts username/password authentication over https, change your remote to be https based rather than ssh based. I hope this helps! If you have any other trouble/questions let me know. Regards, Kevin On Sun, Jul 29, 2018 at 11:18 AM, Krish <[email protected]> wrote: > Hello, > > I've just upgraded from NiFi 1.2.0 to 1.7.1 and been playing around with > the NiFi registry features which are great! > > I've been trying to get it to push automatically to my bitbucket > repository but I keep getting the following error: "Failed to push commits > to origin due to org.eclipse.jgit.api.errors.TransfportException > ssh://git@bitbucketserver:1234/nifi-registry.git Auth Fail" > > In my configuration I have the folllowing setttings in my providers.xml: > <flowPersistenceProvider> > <class>org.apache.nifi.registry.provider.flow.git. > GitFlowPersistenceProvider</class> > <property name="Flow Storage Directory">. > */storage/nifi_registry_repo*</property> > <property name="Remote To Push">*origin*</property> > <property name="Remote Access User">*ssh_key_user*</property> > <property name="Remote Access Password">*ssh key password* > </property> > </flowPersistenceProvider> > > The nifi_registry_repo is a git repo which I have cloned down from my > bitbucket server. > I've setup a SSH and loaded into the bitbucket repo, I can successfully > push and pull from the command line on the nifi registry server using the > ssh key. > > When I change a flow in the NiFi registry UI it commits successfully to > the repo but fails to push the changes up to the bitbucket server. > > Has anyone else done this successfully? Or is there mistake I've made in > my configs? > > Thanks > > K > > >
