locked
Deployment of a Signed Procedure not Working RRS feed

  • Question

  • We are just starting to use signed procedures to handle some security issues. The planned process is as follows:

    1. Generate a certificate c in DB db1 on SERVER s1.
    2. Sign Procedure p in db1 using c.
    3. Get the signature blob from the system tables.
    4. Export certificate c and import it in DB db2 on Server s2.
    5. add signature blob to (exactly the same) procedure in db2.

    Step 5 fails, because the signature does not match. BUT: It's the same certificate and the same procedure.

    If we do exactly the same on a single server using two different databases - then everything works fine...

    Anybody some ideas?

    Apparently, for our deployment scenario we need to use different servers...

    Thanks, Matthias

    Tuesday, June 14, 2011 10:10 AM

Answers

All replies