I followed the article , and tried setting up a secure apache nifi registry. I am having issues with the P12 file. I Persistently get a message stating the password from the password file is not right. I tried this with gnome seahorse and from the command line . From the command line it encounters a parse failure .
Gnome Desktop version 3.22.1 using VTE version 0.46.2 +GNUTLS
seahorse version 3.20.0
keychain 2.8.2 from funtoo.org Inheriting ssh-agent
command line trial
gnome-keyring import CN=sys_admin_OU=NIFI.p12 gnome-keyring: couldn't parse: CN=sys_admin_OU=NIFI.p12
gnome-keyring: couldn't find any place to import files
couldn't parse: CN=sys_admin_OU=NIFI.p12
Tried creating a keyring named NIFI , but this did not get anywhere.
Hoping someone elsewhere could have faced/resolved this or might have a tip .
The default password generated by the toolkit did not work . I regenerated the certificates using the password option, and the certificates were taken in successfully both by windows and CenOS7.
Please treat my query as resolved, as it has cleared my immediate problem.
I have resolved the issue , by providing a password when generating the certificates using the toolkit. With the default password generated by toolkit utility , the P12 file could not be taken in by windows and CentOS7.