It's hard to debug without seeing the actual commands and output.
0) Where do you keep your certificate?
1) Show us the command (and output) you're using to get the proxy
2) Show us the command (and output) you're using to check the
extensions
3) Show us the output of `which grid-proxy-init` and `which openssl`
4) Send the output of grid-cert-diagnostics
Thanks,
Charles
On Aug 11, 2008, at 11:29 AM, I8abyte wrote:
BTW, I don't see any of those extensions on the proxy certs that I
generate (when I run grid-cert-info, "openssl x509" queries, etc.)
On Mon, Aug 11, 2008 at 12:19 PM, I8abyte <[EMAIL PROTECTED]> wrote:
Thanks, I had to rephrase the question: as Charles alluded, how does
one set the path length in the proxy cert? I tried the
grid-proxy-init "-path-length" option but that doesn't help and I
can't see how else to set it.
On Mon, Aug 11, 2008 at 10:57 AM, Joseph Bester
<[EMAIL PROTECTED]> wrote:
On Aug 11, 2008, at 9:08 AM, I8abyte wrote:
Charles--
What options are you using with 'grid-proxy-init' to get the proxy
certificate properties below? How did you set the path length
constraint below? When I run the x509 query on my proxy cert it
doesn't indicate any of the options below ....
Ben--
You can use a sequence like this:
% grid-proxy-init -out /tmp/proxy.pem
% grid-cert-info -file /tmp/x509up_u501.pem
to see the X.509 extensions in the proxy certificate
Joe
