nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Obfuscating form data

geoffb

I have created my own FormType for data fields that are sensitive, so that I can encrypt their values. This works well for ACT_RU_VARIABLE and ACT_HI_VARINST. What I can't figure out is how to have it encrypted in ACT_HI_DETAIL.

The FormProperties are still stored in plain text.

Find more posts tagged with

Comments

trademak

Can you provide some more details about the FormType you've implemented?

Best regards,

geoffb

I basically, just did this in my class that extends AbstractFormType

@Override
def convertFormValueToModelValue(String secretString) {
return new SecretSerialisationType(secretString)
}

frederikherema1

Instead of using a form-type, use a custom variable-type which stores the value encrypted and DON'T use form-properties, they will be always stored the way they come into the submitForm() method…

Another option, if form properties are required, is setting the history level high enough, so form-properties are not recorded…

geoffbullen

What I really want is both to use a form type and to leave the same history level.

Is there a way I can modify how the history stores my particular form type?

frederikherema1

Extract from SubmitStartFormCmd:

 protected Object execute(CommandContext commandContext, TaskEntity task) {<br>&nbsp;&nbsp;&nbsp; commandContext.getHistoryManager()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .reportFormPropertiesSubmitted(task.getExecution(), properties, taskId);<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; TaskFormHandler taskFormHandler = task.getTaskDefinition().getTaskFormHandler();<br>&nbsp;&nbsp;&nbsp; taskFormHandler.submitFormProperties(properties, task.getExecution());<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; task.complete();<br><br>&nbsp;&nbsp;&nbsp; return null;<br>&nbsp; }

The 'history record' is done using the RAW properties-map, as it is passed in. Since the record happens before the "TaskFormHandler" is called, it's also not an option to use a custom TaskFormHandler that alters the values in the properties-map.

The only way I see this working is either we move the "record" of history to after the TaskFormHandler has been executed, although there is no explicit use case for this, as the form-properties are intended to be stored in history as String's, unaffected by the property-type itself. Another way is to do the encryption in the layer above Activiti, if possible.

A solution that can be done without having to modify existing activiti-sourcecode is to create a subclass of the HistoryManager and provide your own factory for this to the processEngineConfiguration. You can override the "reportFormPropertiesSubmitted" method and alter the string-values before you call the super.reportFormPropertiesSubmitted(…).