Bug 747721 - Fuzzy documentation about PIN-generation and creation of Subject for Certificate from LDAP
Summary: Fuzzy documentation about PIN-generation and creation of Subject for Certific...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Dogtag Certificate System
Classification: Retired
Component: Other
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
Assignee: Deon Ballard
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks: 445047
TreeView+ depends on / blocked
 
Reported: 2011-10-20 20:41 UTC by bbonok
Modified: 2015-01-04 23:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-04 20:09:14 UTC


Attachments (Terms of Use)

Description bbonok 2011-10-20 20:41:11 UTC
1. About PIN-generation
 In default setpin.conf there is option 'setpin=yes'. This option create necessary objectclass and attribute. When the objectclass and attribute are created the user have to comment 'setpin=yes', because in setup mode setpin doesn't generate pins.

2. Subject for Certificate from LDAP
 In chapter 9.2.1 in RHCS 8.0 documentation and 9.2.1 in RHCS 8.1 there is notes about creation of Subject in certificate from dnpattern. It doesn't work unless you read B.1.20 in RHCS 8.0 docs and B.2.10 in RHCS 8.1 docs. I didn't find any info in docs to look in Appendix.

Comment 6 Kaleem 2012-01-11 11:38:29 UTC
Verified.

#1.
Following section has been added in section "5.1.3. Usage" of Command-Line Tools Guide for disabling setup mode for setpin tool after creating objectclass and attribute in ldap scehma.
===============
Then, disable setup mode for the setpin command. Either comment out the setup line or change the value to no.

vim /usr/lib/pki/native-tools/setpin.conf

setup=no
========

#2.
Detailed description has been provided in section "2.8.2. Inserting LDAP Directory Attribute Values and Other Information into the Subject Alt Name" of Admin guide.


Note You need to log in before you can comment on or make changes to this bug.