Hi Robert, > I'm new to openxpki and installed the current stable on Buster via the debian > repo. > After several beginner-issues everything works fine now, except if I'm > entering a IPv4 address as SAN field. The approval will then be paused > because of a "backend communication error".
In the majority of use cases your users will be addressing the end entities holding your certifiates by DNS names - and not IP addresses. Hence an IP address does not have to be included in the certificate. My reasoning is that a certificate profile should only include the necessary information to perform the job. If you include more fuzz, it still works, but it's unnecessary fuzz. And once you have introduced unnecessary fuzz into your PKI you will never get rid of it later because you don't know what might break if you do. So don't do it in the first place :) Cheers Martin _______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
