Using a TSA in own signature handler

Question

Good day,
Can someone help me with the steps involve in creating using a TSA inside a custom signature handler api?
When I set the TSA as my default time server as sign my signature field with the normal Adobe Default handler, it uses the TSA and the signature properties reflects this. I wnat to know how I can use a TSA with my custom handler. I sign signature fields using the PROP_PSENG_SignFormatPKCS7DetachedDigest. How can I include a TSA? I've tried adding a TimeStamp dictionary to my SV dictionary of the signature field, but it does not seem to have any affect on the signature...
Any help would be greatly appreciated.
Regards,
Magda

Answer 1

893968 wrote:
BTW, please do not ask me the standard litany of angry-dba questions (why are you doing this? your database is f*****, RTFM, etc.), this is just for my own curiosity. :)Why are you doing this? your database is f*****! RTFM! Etc!! ;-)
SQL is not a procedural language - so you cannot create a view for example that has a parameter signature. E.g. this is possible in a procedural language:
declare
        cursor c( deptID number ) is
                select * from emp where deptno = deptID;
begin
        open c( 1234 ); --// open SQL cursor using a parameter/variable
        --// etc..
        close c;
end;This is not possible using a SQL object like a view. As a view is not a procedure. So the same approach as the above using SQL (silly example, but do demonstrates the basics):
// define
create or replace view emp_view as select * from emp;
// use
select * from emp_view where deptno = 1234;The CBO is clever - and it will likely push such a predicate into the emp_view SQL statement.
To parameterise such a view, is ugly. And should only be considered when dealing with issues such as security and data restrictions. A context is created - this can contain a number of name-values. The view can then use a name-value from the context. Oracle's data dictionary views use this approach.