Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#57 More options for Distinguished Name

closed
nobody
None
5
2014-11-22
2011-07-10
Christ Schlacta
No

Certificates can be created with other configurations for the DN instead of the common O=,C=,OU=,S=,CN=,E=,L= format. for example, I have one based solely on 0.DC=,1.DC=,OU=,CN=, and I cant even find domainComponent as an option. The default setup is unsuitable in many applications, and should be used as a guideline only. the 0.DC,1.DC,OU,CN layout matches an existing LDAP infrastructure, and therefore is suitable to my needs specifically, however, the ability to so customize will be of use to many people. I think the default displayed boxes near the top of the form should be overridable on a per-database basis as well, if feasible.

Discussion

  • The content of the subject can be freely configured by using the box below the default DN entries. This can be used by advanced users like you.
    The "domainComponent" can be added by adding it to "dn.txt"
    Providing the most usual components for the average user is IMHO a good idea.

     
  • I agree that sensible defaults are a great idea, and as they are is awsome, however, I also observe that the default set of 8 textboxen up top provide that well. I propose that the user should be able to override which boxes are presented there. having to add custom elements for every certificate in the space provided will get tedious, even with the use of templates. an option to override them would go a good distance toward usability.

     
    • status: open --> closed
    • Group: --> Next_Release_(example)
     
  • commit dcd940b6b89900c9365e1d88055b4adf01f3f80c
    Author: Christian Hohnstaedt christian@hohnstaedt.de
    Date: Wed Nov 12 22:57:37 2014 +0100

    SF Feat. Req. #57 More options for Distinguished Name
    
    Make explicit DN subject entries configurable
    per database.