Adapt versioning mechanism

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

wolfc01

Hi,

I like to adapt the versioning mechanism of content services as follows:

- When checking in an existing word/excel document: change version number from 0.1 -> 0.2 (this is already the case)

- When the version number must be 1.0, 2.0, .... then the word/excel document is to be checked for the presense of one or more digital signatures. Otherwise Alfresco should not accept the document and regard the upload as failed.

Reason: in our company, all documents having a   x.0 version are regarded as 'released'  and therefore need to have digital signatures in it. So: alfresco should deny a document having no signatures in it having version x.0.

We have already .NET programs to check signatures in the documents, it then would be nice if server side those executables could be called from Java to perfom the signature checking.

Br,

Carl.

angelborroy

You should invoke those NET components using command line from Java or so.

Alternatively, you can use some Java code in order to check if a document includes a digital signature. You can take this code/project as sample:

https://github.com/keensoft/alfresco-esign-cert/blob/master/esign-cert-repo/src/main/java/es/keensoft/alfresco/behaviour/CustomBehaviour.java#L179