Hi, in case anyone else facing this issue maybe it's not the ideal solution, but I solved it by adding the following line to the token configuration directly
INIT_ARGS = connector=http://127.0.0.1:12345 Thanks all On Fri, Sep 29, 2023 at 8:31 AM Martin Bartosch via OpenXPKI-users < [email protected]> wrote: > Hi, > > > Am 29.09.2023 um 04:08 schrieb Lixin Liu <[email protected]>: > > > > I am using RHEL system which is not officially supported. But from what > I see, there are > > only very minor difference. I have these: > > Just to clarify: The Community Edition is available as source code and > packaged for Debian. However, OpenXPKI Enterprise Edition is available > packaged for Red Hat Enterprise Linux, SuSE SLES and Ubuntu LTS. > > Any HSM that can successfully be used on the command line with OpenSSL via > PKCS#11 should also work with OpenXPKI. How this exactly works depends on > the HSM and its PKCS#11 implementation. > > Some hints: > - it has already been mentioned, but make sure that any environment > variables the driver needs is also set in OpenXPKI > - personally, I very much prefer the RFC 7512 URI scheme for specifying > PKCS#11 objects (keys) in the OpenXPKI configuration instead of the > traditional (and somewhat obscure) slot notation. The GnuTLS p11tool is > very useful in getting the proper information needed for a particular HSM. > > Otherwise the suggestions provided on the list should help get this up and > running. > > Cheers > > Martin > > > > > _______________________________________________ > OpenXPKI-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openxpki-users > -- *Regards* *Montajab Saleh*
_______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
