Bug 1476 – grid-cert-request directions should be generalized

Bug 1476 - grid-cert-request directions should be generalized

Summary:

grid-cert-request directions should be generalized

Status:	NEW

Product:	GSI C
Component:	Credentials and Proxies
Version:	unspecified
Platform:	All All

Importance:	P3 enhancement
Target Milestone:	4.0
Assigned To:	Laura Pearlman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2003-12-19 11:05 by Von Welch
Modified:	2008-08-11 14:54 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Von Welch 2003-12-19 11:05:31

We should rip any reference to the Globus CA out of grid-cert-request.

We should point folks at GCS with some text like what is below:

-quote-
We strongly encourage those who have access to one of the many
high-quality CAs being run by production Grids, to use that CA.

For others, we offer the Globus Certificate Service for aquiring
certificates. For more information please see:

http://gcs.globus.org:8080/gcs/
-end quote-

------- Comment #1 From Sam Meder 2003-12-19 11:44:13 -------

There is no reference to the globus ca in grid-cert-request. It is also used by
simple CA so I don't think we should put in a pointer to GCS.

------- Comment #2 From Von Welch 2003-12-19 13:41:54 -------

Makes sense.

Does it make sense to have a text file in /etc/g-sec/ that gcr just dumps out if
it's present? The CA setup gpt package could install it then and it could have
whatever directions the ca wanted.

------- Comment #3 From Sam Meder 2003-12-19 14:06:53 -------

We could do that, shouldn't be too hard.

------- Comment #4 From Sam Meder 2005-02-03 06:10:00 -------

*** Bug 2686 has been marked as a duplicate of this bug. ***

------- Comment #5 From Sam Meder 2005-03-25 14:28:57 -------

*** Bug 3015 has been marked as a duplicate of this bug. ***

------- Comment #6 From Sam Meder 2005-04-06 16:30:54 -------

Directions can now be externalized by providing a "directions.<ca hash>" file
in
the setup package. This file can contain three sections delimited by:

----- BEGIN ${SECTION_NAME} TEXT -----
----- END ${SECTION_NAME} TEXT -----

where ${SECTION_NAME} is one of:

REQUEST HEADER
USER INSTRUCTIONS
NONUSER INSTRUCTIONS

Reassigning to Laura for the change to the gcs setup package.

------- Comment #7 From Sam Meder 2005-04-14 12:50:05 -------

I've updated the GCS setup package with the new directions and updated the gcs
pages (in cvs) to point at the new setup package. Reassigning to Laura so she
can push out the changes to the running site.

/Sam

------- Comment #8 From Olle Mulmo 2005-05-13 10:23:52 -------

Feedback from David Groep, head of the European GridPMA:

[begin]
Any reason why the naming of the directions-file is "contrary" to the
resulat naming scheme?
We already have:

  <hash>.0
  <hash>.r0
  <hash>.signing_policy
  <hash>.crl_url

and now suddenly we get

  directions.<hash>

??? 
[end]

I must say I agree and that we should consider supporting <hash>.directions (as
well).