-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SMP lookup doesn't work properly #11
Conversation
Hi Pavel! |
Hi Philip! |
No problem - your welcome. |
And the problem in this example is the uppercase document type ID - maybe I was telling this to Hatem by accident. Should be case sensitive (see POLICY 3) |
Yes, but I think this is not a problem. |
I modified your code slightly - the uppercase document type ID should not work |
According to https://peppol.helger.com/public/locale-en_US/menuitem-tools-participant?scheme=iso6523-actorid-upis&value=0088%3A5060510050006&sml=digitprod&action=perform all docType IDs are lowercase on your side |
This is not our SMP |
You're right but: |
Looks like the issue in SMP implementation |
I added an example DocType ID in uppercase and it is shown correctly: |
When opening Changing to http://test-infra.peppol.at/iso6523-actorid-upis%3A%3A9915%3Atest/services/busdox-docid-qns%3A%3ABLA-foo-FASEL%3A%3ALOCALRoot%23%23urn%3Awww.cenbii.eu%3Atransaction%3Abiitrns014%3Aver2.0%3Aextended%3Aurn%3Awww.peppol.eu%3Abis%3Apeppol5a%3Aver2.0%3A%3A2.1 (lowercase "foo") fails as expected. But changing to http://test-infra.peppol.at/iso6523-actorid-upis%3A%3A9915%3ATEST/services/busdox-docid-qns%3A%3ABLA-FOO-FASEL%3A%3ALOCALRoot%23%23urn%3Awww.cenbii.eu%3Atransaction%3Abiitrns014%3Aver2.0%3Aextended%3Aurn%3Awww.peppol.eu%3Abis%3Apeppol5a%3Aver2.0%3A%3A2.1 (uppercase "TEST" in participant ID) works So it must be something in your SMP implementation |
I wrote before that this is not our SMP (I don't know which implementation they are using). |
SMP lookup doesn't work if ProcessIdentifier defined in uppercase on server
In the example the first smpClient.getEndpoint() returns the endpoind but the second call - returns null