October 2020 - Pki-users - Dogtag PKI List Archives

Automatically generate certificates without approval
by Wahaj K 05 Nov '20

05 Nov '20

Hi Guys, I am new to Dogtag PKI and have installed it on fedora 33. I am able to send a PKCS#10 certificate, approve and then get the issued certificate. I need to know a way to generate the certificate without manual approval hence when PKCS#10 request is sent ,the certificate is generated right away. I have looked at profiles, CA configuration but couldn't see a way. I am using Dogtag 10.9. Is this possible? Any guidance is appreciated. Regards, Wahaj

3 3

Some questions about dogtag Replicate
by Jose Antonio Mendoza Roa 09 Oct '20

09 Oct '20

Hi folks I have some doubts How is the better step for configure replication of dogtag-pki Im read this manual and it's very confusing for me . Now i have running dogtag-pki-10.5.1-2.el7pki.noarch in one server1 (RHEL 7.x) But i need to replicate in the other server2 in case of failure this server1 Im read this manual https://www.dogtagpki.org/wiki/DS_Replication_Setup -Firs Question in server1 i have modified 3 profiles in dogtag PKI (how to replicate this configuration in the server2) -Second Question in server1 i have some certs ssl how to replicate this certs to server 2 -- Ce courrier électronique et les fichiers qui y sont annexés peuvent renfermer des renseignements privilégiés et confidentiels à l'intention exclusive du destinataire. Si vous n'êtes pas le destinataire, vous n'êtes pas autorisé(e) à utiliser, à copier ou à divulguer à un tiers le contenu de ce courrier électronique ni des fichiers joints. Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l'expéditeur immédiatement par courrier électronique et détruire ce message ainsi que les fichiers en annexe. This electronic mail message -- and any attachments -- may contain privileged/confidential information, intended only for the use of the addressee. If you are not the addressee, you may not use, copy or disclose to a third party the content of this message or its attachments. If you have received this message by mistake, please notify us immediately by e-mail and destroy this message, along with all attachments

2 1

Clarification needed
by Pascal Jakobi 08 Oct '20

08 Oct '20

Page : https://www.dogtagpki.org/wiki/Keycloak (This is for setting Keycloak in front of dogtag) Page says "store the configuration in <web application>/WEB-INF/keycloak.json" (referring to the keycloak client configuration). But what is the "<web application>" ? I am very unsure.... More generally, it would greatly help is more explanations were given in the page... -- *Pascal Jakobi* 116 rue de Stalingrad 93100 Montreuil, France pascal.jakobi(a)gmail.com - +33 6 87 47 58 19

2 1

Dogtag PKI is migrating issue tracker from Pagure to GitHub
by Dinesh Prasanth Moluguwan Krishnamoorthy 05 Oct '20

05 Oct '20

Dear users, developers and maintainers of PKI, We, the Dogtag PKI team, have decided to use GitHub issues as our primary issue tracker. As a part of the effort to keep things unified, we will be migrating all the issues (open and closed) from Pagure Issues <https://pagure.io/dogtagpki/issues> to GitHub Issues <https://github.com/dogtagpki/pki/issues>. We see several advantages by this migration: 1. Reported issues and code stay closer 2. Better ways to refer/track issues within PRs and commits 3. Better audience outreach When? Migration starts on Friday, Oct 2 (~5PM EST) and we anticipate it to end by Oct 4. Dry Run Results https://github.com/pki-bot/pki-issues-final/issues Process: We are planning to do the migration in 4 stages. *Stage 1 (~5 hours):* Copy all issues from Pagure to GitHub. We have identified and tried to map the users from Pagure to GitHub. If your nickname is listed in [1], you’ll be receiving github notifications and/or emails. Unfortunately, there is no way to keep it down. *Stage 2 (~2 hours):* This is a check stage where we test if every Pagure issue has been copied to GitHub correctly. There will be no notifications generated *Stage 3 (~2 hours):* Add comments to ALL pagure issues and close ALL OPEN pagure issues as Migrated. The comment will include a link to the corresponding GH issue. We have placed a request [2] to turn off notifications during this stage. *Stage 4 (~1 hours):* Update associated bugzilla with link to new GitHub Issues. The “Devel Whiteboard” will be updated in the format `PKI <GH issue number>` and an external tracker to the GH issue will be added. There will be no notifications generated in this stage. Migration Tool: The tool is available in GH: https://github.com/SilleBille/pagure2github/ Problems? In case you find any bugs or problems in the migrated tickets, feel free to reach out to us via pki-users(a)redhat.com Dogtag PKI Team [1] https://github.com/SilleBille/pagure2github/blob/master/lib/pagure2github/_… [2] https://pagure.io/fedora-infrastructure/issue/9361

1 1