You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2024/10/08 10:28:00 UTC

[jira] [Assigned] (CAMEL-21328) Camel-AS2 signing MDN message with SHA1 and MD5 not sha-256

     [ https://issues.apache.org/jira/browse/CAMEL-21328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-21328:
-----------------------------------

    Assignee: Claus Ibsen

> Camel-AS2 signing MDN message with SHA1 and MD5 not sha-256
> -----------------------------------------------------------
>
>                 Key: CAMEL-21328
>                 URL: https://issues.apache.org/jira/browse/CAMEL-21328
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-as2
>    Affects Versions: 4.8.0
>            Reporter: RAVI
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.8.1, 4.9.0
>
>         Attachments: AS2MicAlgorithm-old.java, AS2MicAlgorithm.java
>
>
> Hi Team,
> I currently don't have a workaround for this issue and would appreciate your insights.
> In my AS2 receiver application, which uses the Camel-AS2 dependency, we receive messages with {{micalg=sha-256}} from the sender. However verification at sender is failing though the latest 4.8.0 Camel-AS2 code is referring all possible algorithms which were not in previous versions, as shown in the attached files.
> Is there a need to add another entry in constants file with sha-256 ( - in between)
> {color:#000000}String {color}{color:#0000c0}SHA_256_AS2_ALGORITHM_NAME{color}{color:#000000} = {color}{color:#2a00ff}"sha-256"{color}{color:#000000};{color}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)