Torsten Lull

Other values like "OCSP service Default URI" can be changed and saved. No, I haven't enabled debug log. The yellow fields prevent renewing a CA. But it worked when the fields were cleared. When you look into the CA configuration after renewing it, the content of the 2 fields in question appear again. I'm using firefox. I guess first I upgrade my production environment to 7.11.0 and check the situation again. Many thanks so far!

Okay, my testing environment is running 7.11.0. My plan is now to upgrade the production PKI to 7.11.0. So If I understand you right I can have the hope that the problem will be gone after upgrading.

I tried it again and created 3 screenshots: 1. open CA for editing and showing current state 2. clear the 2 fields in question and press save 3. open the CA again for editing -> the 2 fields in question are filled again Is it dangerous to clear the fields directly in the database? In my case the fields should be empty. Kind regards, Torsten

Do you mean I should post my question again in https://github.com/Keyfactor/ejbca-ce/discussions?

In general should it be possible to clear both values? No, we do not run any custom code. It is a default deployment and it has been running for over 10 years.

Hello, I'm running EJBCA 7.4.3.2 CE. Now I detected that 2 values in all CA definitions are filled with values: - "CA issuer Default URI" filled with random hex number and is marked with a yellow background - "CMP RA Authentication Secret" filled with a hidden value and is marked with a yellow background I have never set these values. In addition I have running an older copy of the database as a testing system. In this system all these fields are empty. After clearing the fields and saving the CA,...

The logging in question is caused by Java Util Logging loggers. By using the bridge jul-to-slf4j it is possible to catch and/or suppress this logging.

Some years ago I have switched from generating my own WS client stub by using wsimport to using your delivered classes. For instance my entry point into the EJBCA world is the class org.ejbca.core.protocol.ws.client.gen.EjbcaWSService.EjbcaWSService