(These difficulties may be an argument to strongly discourage using
just an Originator-ID-Asymmetric field unless you know the recipient
already has the certificate.)
- Jeff
I want to think about it some more, but I am beginning to think
that the requirement to have this alias should be included in the
StrongAuthenticationUser object class. But until I understand how
aliases work across ADDMDs, I'm not sure just how to proceed.
Bob
Let me ask the following question: Why have an
Originator-ID-Asymmetric field at all when an Originator-Certificate
workds just fine? Why was it put in the standard? It is an
implementor's nightmare.
- Jeff