Hi Mukilan,

the DN is determined by the template you see in the profiles which gives you the options to work with the values from the PKCS10 container.

Passing DN parts directly into the subject parser is covered only by the workflows shipped with the enterprise edition and not included in the community edition. We therefore will not provide this kind of support here on the ML - feel free to reach out to us for a commercial support offer.

Oliver

Dear Oliver,

Thank you very much for your answer.

The csr_key_alg and csr_subject_key_identifier will not be useful in Subject DN or SAN but I would like to know how I can refer it in profile template. As you said, it is not possible because of underlying used structures.

The main goal is to change the Subject DN according to the company policy before issuing certificate. The modified subject DN will be passed as extra argument in RPC API as like below

Inline image


How can I parse the mod_subject and merge those information into the used structures ie C, OU,O etc. I am trying some workflow steps like below

set_subject_hash:
        class: OpenXPKI::Server::Workflow::Activity::Tools::SetContext
        param:
            _map_subject_hash: >
                [% substr1 = context.mod_subject;
                SET context.subject_hash = {};
                FOREACH pair IN substr1.split( /[,=]/ );
                    IF context.subject_hash.exists( pair.0 );
context.subject_hash.set( pair.0, context.subject_hash.get( pair.0 ) _ ', ' _ pair.1 );
                    ELSE;
context.subject_hash.set( pair.0, pair.1 );
                    END;
                END %]
                $context->{subject_hash}

But getting some parse error

Inline image


I need some help in Perl Template Toolkit to write workflow steps. Please help me.

Regards,
Mukilan

On Friday, 13 January, 2023 at 07:02:39 am GMT+1, Oliver Welter <[email protected]> wrote:


Hi Mukilan,

the subject and SAN rendering happens based on the information entered via the profile fields or in case of enrollment the data read from the CSR. This is hardcoded in the underlying activity code and can not be changed by configuration.

I do not understand what you want to achieve and how this information is useful in the DN/SAN but the only way would be to add some workflow steps to merge this information into the used structures or write your own activity.

Oliver

On 11.01.23 14:58, Mukilan P via OpenXPKI-users wrote:
Hello Experts,

If somebody throws some light on this, it will be great.

Regards,
Mukilan

On Thursday, 5 January, 2023 at 04:03:54 pm GMT+1, Mukilan P via OpenXPKI-users <[email protected]> <mailto:[email protected]> wrote:


Hello Experts,

How do we refer Workflow Context variables (for example csr_key_alg, csr_subject_key_identifier, etc)in profile template while rendering subject?


Regards,
Mukilan
_______________________________________________
OpenXPKI-users mailing list
[email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/openxpki-users <https://lists.sourceforge.net/lists/listinfo/openxpki-users>


_______________________________________________
OpenXPKI-users mailing list
[email protected]  
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/openxpki-users  
<https://lists.sourceforge.net/lists/listinfo/openxpki-users>
--
Protect your environment -  close windows and adopt a penguin!
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users


_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users

--
Protect your environment -  close windows and adopt a penguin!
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users

Reply via email to