On Mon, Dec 19, 2011 at 5:36 AM, John Dennis jden...@redhat.com wrote:
Sorry, but currently on the command line the only way to specify a
certificate is via it's serial number. The serial number is the only
identifier guaranteed to be unique. However, I agree it's not convenient.
Would you
On 03/13/2012 04:44 PM, Stephen Ingram wrote:
On Mon, Dec 19, 2011 at 5:36 AM, John Dennis jden...@redhat.com wrote:
Sorry, but currently on the command line the only way to specify a
certificate is via it's serial number. The serial number is the only
identifier guaranteed to be unique.
On 03/13/2012 05:29 PM, Stephen Ingram wrote:
On Tue, Mar 13, 2012 at 2:25 PM, Dmitri Pal d...@redhat.com wrote:
Thank you!
Just FYI, all tickets go into NEEDS_TRIAGE bucket first so that we do
the correct processing and handling when we triage them.
Got it. Sorry about that. I guess that's
On 12/18/2011 09:05 PM, Stephen Ingram wrote:
On Mon, Dec 5, 2011 at 12:49 PM, Rob Crittendenrcrit...@redhat.com wrote:
...snip...
Be sure that the CN value is the FQDN of your server.
IPA server:
# ipa cert-request --prinicipal HTTP/remote.example.com /path/to/csr.pem
# ipa service-show
Stephen Ingram wrote:
On Wed, Nov 30, 2011 at 12:59 PM, Rob Crittendenrcrit...@redhat.com wrote:
The only part assuming that is ipa-join itself. IPA does not support the
direct use of kadmin or kadmin.local. On a supported platform you'd run:
# ipa-getkeytab -s ipa.example.com -k
