Hey, what do you know? Seems like this is fixed before we started any work on it! If only all issues were this easy
I will update the JIRA issue to reflect the requirement for documentation on this.
I was missing "securementSignatureKeyIdentifier" with proper value..... It will be better if we update documentation.