Jorge Redondo Flames wrote:
Yeah! The form should be prefilled, but it is not. Can you give a starting point to get this bug fixed?
The form is generated by basic_csr and usually basic_csr should evaluate the input from the token request. The trick is that the generate key button in the form set the subject and all the other intput variables plus a special state variable (operation) which signalize the base_csr script that the next step is the key generation or the check of the input data.
Usually the data fro the token request is placed in several hidden fields if you view the CSR (please see src/common/lib/cmds/viewCSR line 253 to 272). These hidden fields are used by basic_csr if the "generate key" button is pressed. The error must be in the lines 55 to 108 from basic_csr.
Perhaps we forgot to migrate the handling of the token request parameters during a rewrite of basic_csr. I think we must include a check before the for-loop which looks for parameters with special names like cn or email and if these parameters are found then we must map them to "DN_VALUE_$i" parameters if we find a matching getRequired("DN_TYPE_".$type."_ELEMENT_".$i). I only take this directly from the code in basic_csr.
The best patch would be a change of the code in viewCSR. Here we should set the correct hidden fields for basic_csr and not only cn and email.
Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
smime.p7s
Description: S/MIME Cryptographic Signature
