search

phax / phoss-smp

phoss SMP - a Peppol and OASIS BDXR SMP Server, CEF eDelivery compliant
128 stars 37 forks source link

Question About Participant ID forced lowercase #183

Closed Legione85 closed 2 years ago

Legione85 commented 2 years ago

Hi,

I'm using the phoss 5.2.0 and when I'm creating a new service group from the UI it's always created in lowercase.

Seeing some scheme ID (for the example the 0210 ) it seems that for the rules it requires uppercase letters.

There's a way in the configuration to not force the lowercase on the UI?

Maybe I'm missing something on the rules of the Peppol network

Any advice or reference will be appreciated.

Thanks

phax commented 2 years ago

Hi @Legione85, Thanks for asking :) That is a bit tricky, but it is correct for the usage in Peppol. As you can read in the Peppol Policy for use of Idenfiers (https://docs.peppol.eu/edelivery/policies/PEPPOL-EDN-Policy-for-use-of-identifiers-4.0-2019-01-28.pdf), in Policy 2: "All Participant Identifier values have to be treated case insensitive even if the underlying scheme 126 requires a case sensitive value."

And that is why the SMP does this lowercasing - to handle the participants "case insensitive". But it only does it, if the SMP is configured in "peppol" mode and if the participant identifier scheme is "iso6523-actorid-upis".

hth

Legione85 commented 2 years ago

thanks Philip,

I think this reference should settle any controversy, until this policy is not modified of course

phax commented 2 years ago

This policy is one of the cornerstones of Peppol and I don't see why this should be changed, as this would be very disruptive. Don't forget to update on v5.4.3 because of the Log4J issue....