Replies: 1 comment 3 replies
-
Warning! Adding custom DN attributes is one of the thing I would warn against most. If you are interested in some standard DN attributes that EJBCA does not support, I'd rather recommend raising that as an issue, or preferably a PR. Adding your own poses a long term risk for upgrades. I.e. you have to maintain it yourself, and if EJBCA ever addes it as a standard attribute you will get into bit problems. (as the warning in the properties file says). I will update the properties file for the next release btw. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello the EJBCA team,
I think the src/java/profilemappings.properties should be updated. Indeed, linde 26, one reads that custom attributes have an ID from 200 to 299; while, lines 111 and 113, one reads that custom IDs are from 300 to 399.
First issue:
What's true? I tend to believe that it is the 300-399 range, given the content of SshEndEntityProfileFields.java
Second issue:
using an old EJBCA version, I have created many certificates with a custom atribute whose ID is 200.
To compile the latest version of EJBCA, I will change the src/java/profilemappings.properties file and assign the ID 300 to my custom attribute.
The question is: will I encounter any problem with such a change of ID?
Thank you for your help.
talcher
Beta Was this translation helpful? Give feedback.
All reactions