Partnership checks differs between Xml definition and DB definition

[davideyeahsure]

I've updated our production system to use the DbPartnershipFactory for partnership definition, I've created the database by importing the XML definition with a script. One of our partner has an "encrypt" option specified as "aes-256" ,this has been reported in the db as it was in the xml:

<partnership name="ECCGITEST-to-HMS">
   <sender name="ECCGITEST"/>
   <receiver name="HMS"/>
   <attribute name="protocol" value="as2"/>
   <attribute name="as2_url" value="https://xxxxxx:1443/"/>
   <attribute name="as2_mdn_to" value="team@xxxxx.net"/>
   <attribute name="as2_mdn_options" value="signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, SHA256"/>
   <attribute name="encrypt" value="aes-256"/>
   <attribute name="sign" value="SHA256"/>
</partnership>

In the db is:
select * from partnership_attribute where partnership_id=346;
+------+----------------+-----------+-----------------+-------------------------------------------------------------------------------------------+
| id | partnership_id | category | attribute_name | attribute_value |
+------+----------------+-----------+-----------------+-------------------------------------------------------------------------------------------+
| 2388 | 346 | attribute | as2_mdn_options | signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, SHA256 |
| 2387 | 346 | attribute | as2_mdn_to | team@xxxxxxnet |
| 2386 | 346 | attribute | as2_url | https://xxxxxx:1443/ |
| 2389 | 346 | attribute | encrypt | aes-256 |
| 2385 | 346 | attribute | protocol | as2 |
| 2390 | 346 | attribute | sign | SHA256 |
| 2391 | 346 | attribute | subject | File $attributes.filename$ sent from $sender.name$ to $receiver.name$ |

Both the XML and the db are loaded with no issues at startup, but when processing an AS2 message, with the xml file it works fine, but with the DB I get the error:

ERROR org.openas2.processor.sender.AS2SenderModule -- Unsupported or invalid algorithm: aes-256
java.security.NoSuchAlgorithmException: Unsupported or invalid algorithm: aes-256

Using AES256 it works.

Is the checking different betwen the two method? And why is not reported as an error during loading of the database?

Davide

[uhurusurfa]

I am unsure why it works for you with XML based config at this stage because the correct algorithm identifier is "aes256" and the compare is done case insensitively so really you should not have been successful using XML config.

I did a quick test using XML config with "aes-256" and it failed:

18:14:52.171 [AS2DirectoryPollingModule] ERROR org.openas2.processor.sender.AS2SenderModule -- Unsupported or invalid algorithm: aes-256
java.security.NoSuchAlgorithmException: Unsupported or invalid algorithm: aes-256