James, > For the 'openxpkicli import_certificate' command there is a additional > parameter named 'profile' which takes a string argument. Is this string a path > to a file; or just the name of a file; or something else?
Well, it's the profile name... In terms of the OpenXPKI configuration tree, this value references a leaf node below the "profile" node of a realm. In case of our published example YAML configuration layout (courtesy of Config::Merge), this also happens to be a file name in the profile directory of the realm. > > openxpkicli --realm hll_ca2016 \ > --filearg data=bare_20160001.pem \ > --param pki_realm='hll_ca2016' \ > --param update=1 \ > import_certificate > > Is the profile parameter significant in placing an imported certificate into a > specific realm? I don't understand the question. If you want to associate the imported certificate with a profile, you can specify it as an option for the import_certificate API function. > Is the default.yaml a valid profile for the purpose of importing a certificate > into a specific realm? No, as the name suggests it contains the common defaults for all other defined profiles. Cheers Martin _______________________________________________ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users
