Hi.
We were having a similar problem and worked around by changing the
Apache config. It's probably not the best solution but it worked for us
without having to dig too deep into the OpenCA configuration and
possibly break our whole infrastructure...
These are the important settings in the httpd.
Hello Matthias,
Thank you for response.
> Hello,
>
> sounds for me a little bit complicated. Isn't it enough to protect the
> server for example with .htaccess and each person will get its own
> username / password.
The thing is that I am going to restrict the access on some public
interface pages
Hello,
sounds for me a little bit complicated. Isn't it enough to protect the
server for example with .htaccess and each person will get its own
username / password.
Moreover normally the certificate request is to be checked at the ra
site thus you could only prevent someone from bringing in a lot
Hello,
I have the following problem.
I have deployed the OpenCA public interface on my machine (with OpenCA
0.9.3-rc1).
This interface has pages where system administrators can request
certificates for hosts and services.
I need to restrict access to these pages to the persons, possessing a
val
