Verify your certificate is properly inserted into Microsoft's local certificate manager store (certmgr.msc) then sign your .ma (rsign.exe) using the certificate common name (-cn) and sign your .dll (dllsign.exe) similarly. If any errors occur Generate a MicroStation digital signature diagnostics log as follows:

 

MS_SECURITY_DIAGNOSTICS= 1

MS_CONSOLELOG=c:\ustnlog.txt

 

Attached is Digital Rights Impact on Application Development; an older document providing an overview of MDL application signing: process, tools, and additional validation steps.

 

This is an example that shows how to manually sign your .ma file (vs. rsigncmd in your .mke/.mki file) you may want to try using -cn (common name) of the certificate; like this:

 

rsign -cn "Bentley Developer Support" myapp.ma

 

To validate an MDL application (.ma, .mvba, or .dll) signature:

 

checksignature --ll myapp.ma

checksignature --ll myapp.mvba

checksignature --ll myapp.dll

Alternate ways include:

checksignature -x myapp.ma, or

rdump -t'dSig' myapp.ma

For additional information on Signing Applications for use in MicroStation Security Modes see topics: Digital Signatures and Tools for Signing.