CLEANACCESS Archives

July 2008

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Hennessey, Sean" <[log in to unmask]>
Reply To:
Cisco Clean Access Users and Administrators <[log in to unmask]>
Date:
Wed, 9 Jul 2008 13:59:36 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
It was the actual CA. It would have been the same CSR (I guess) as I
just generated the PEM from the one that's currently in place. From what
it looks like in Cisco's TAC instructions, you have to generate a new
request by creating a new temporary cert. Not a tough solution but a
serious pain in the patootie, I don't mind saying...

:)

- Sean

----

Sean Hennessey

Networking and Information Security Systems Administrator

The University of Portland


-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Nathaniel Austin
Sent: Wednesday, July 09, 2008 1:41 PM
To: [log in to unmask]
Subject: Re: Cert Question

Interesting. Is it CCA saying that the CSR was previously used, or the 
actual CA saying that?

I'm pretty sure I've done it on a Microsoft CA before, but have never 
tried it with an external CA. Maybe the CSR is the same as it was last 
time you asked for a cert from them and so they reject it.

Nate 

ATOM RSS1 RSS2