Versions Compared

Old Version 22

changes.mady.by.user Serge Libert

Saved on

compared with

New Version 23

changes.mady.by.user Serge Libert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fall 2020 update - hsmp mtci schedule and doc update announcing the user testing phase

...

Contents

Table of Contents
maxLevelminLevel2
minLevelmaxLevel2
absoluteUrltrue

9956>0208 migration

...

since smp.belgium.be throws a BELMA-306 error code upon attempt to register a non-BIS (3.0) document type prior to registering the equivalent BIS

The belgian Governement takes measurs to phase out all non-BIS (3.0) traffic reaching it. old BIS receiving capability will be removed (a) from the test environment on and from production on

a change is planned to also reject old BIS (2.0) registration. this is a new step towards BIS and BIS BILLING migration completion/cleanup.

...

In order to speed up the migration of Belgian enterprises out of Hermes towards a suitable e-invoicing tools, BOSA (a) decided to

  1. initiate migration for all Hermes participants and

...

  2. let HermeSMP expose a (secure) migration Token collection interface.

The interface specifications were submitted to e a review round to the Belgian SP/AP forum members in June 2020. The first stable version of the specs were posted below on . The specs interface is ready for tests as of The specs are maintained below.

Specifications

  1. Swagger: hsmp_migration_key.yaml

  2. Test Plan:

    Postman

    : HSMP_migration_key.postman_collection.json (Postman)

  3. Comments:

    • the test plan will be functional once the development is done. In the meantime, it is to be used as reference for preparation purposes by the SPs who will contribute to the tests and validation phase.

    • the test plan may be enriched by additional test cases in a later phase

  4. Additional documentation:

    1. https://documenter.getpostman.com/view/11381713/T17FCUqp?version=latest

    2. pay attention: this service allows a maximum of 1000 collections per day. the system will blacklist any user exceeding this level. The affected user will have to contact BOSA (service owner) to request reactivation. As an alternative, the user planning to exceed 1000 collections a day, can contact BOSA to schedule the operation. He will then be temporarily authorized to exceed the limit mentioned above.

    3. Schedule: see table below

  5. Version history
    This section will report the publication of updates of the documentation, if any.

    1. Initial draft published for review purpose

    2. First stable version published along with initiation of development works

  6. Additional documentation:

    1. https://documenter.getpostman.com/view/11381713/T17FCUqp?version=latest

    2. pay attention: this service allows a maximum of 1000 collections per day. the system will blacklist any user exceeding this level. The affected user will have to contact BOSA (service owner) to request reactivation. As an alternative, the user planning to exceed 1000 collections a day, can contact BOSA to schedule the operation. He will then be temporarily authorized to exceed the limit mentioned above.

    3. list of responses codes: see table 1 below

    4. Schedule: see table 2 below

  7. Version history
    This section will tracks the publication of updates of the documentation

    1. Initial draft published for review purpose

    2. First stable version published along with initiation of development works

    3. ready for acceptance testing. resources HSMP_migration_key.postman_collection.json, hsmp_migration_key.yaml and https://documenter.getpostman.com/view/11381713/T17FCUqp?version=latest updated. overview error codes added. planning updated.

table 1 - responses

scenario

request

response : http response code - detailled response

positive

valid and not yet migrated enterprise number

200 - OK - the pair enterprise number & migration token

security 1

certificate missing

401 - HSMP-802: no certificate supplied with the request

security 2

error while parsing certificate

401 - HSMP-803: error while parsing client certificate

security 3

certificate expired or not yet valid

401 - HSMP-804: client certificate expired or not yet valid

security 4

added : not trusted

401 - HSMP-805 :Certificate cannot be trusted by PEPPOL trustStore

security 5

added : Test/Prod mismatch

401 - HSMP-806 : Certificate environment does not match with requested environment (test or prod)

security 6

added : not a PEPPOL AP

401 - HSMP-808: Certificate is not a PEPPOL ACCESS POINT certificate

error 1

the enterprise number does not correspond to an existing enterprise (or is garbage)

404 - HSMP-001: invalid or non-existing enterprise number + id

error 2

the enterprise number was deleted (in the context of the monthly processing of the CBE dump or the admin removal function)

404 - HSMP-012: inactive enterprise number + id

error 3

the enterprise number that was already migrated to another smp

404 - HSMP-013: already migrated + id

error 4

any request of a user that exceeded the blacklisting limit and was not yet reactivated

403 - you have been blacklisted please contact BOSA

error 5

added : any request of a user that broke a network global limit, and was not yet reactivated

403 - HSMP-812 : Global limit reached. Please contact BOSA

error 6

added : any request of a user that broke an IP-specific limit, and was not yet reactivated

403 - HSMP-813 : Limit reached for IP. Please contact BOSA

error z

internal server error

500 - HSMP-999: The service encountered an internal error

table 2 -Schedule and progress

ATTENTION: Schedule update 16 Jul : original schedule is revised as follows: user testing is postponed 1 monthsplit in two.

pulished babelway ONGOING

phase

time

what

status / comment

design

JUNE

  • AP forum: discuss the interface specifications, practicalities

  • then post a draft proposal to collect comments (2weeks)

  • then publish (initial) documentation package ( swagger + Test plan + read-me ) and schedule on agreed repository

DONE: initiated → open for comments until → review closed → first stable version of specs

published

development and

Tradeshift test

JULY - AUGUST

includes update of the documentation package at end of dev phase

DONE

user testing

SEPTEMBER

includes collection of test results, fixing, updating the documentation package

scheduledand teh code if needed

  • sub phase 1: early bird testing with close support by Tradeshift : -

  • sub phase 2: wide-scale testing with any volunteer with BOSA support (Tradeshift in L2): -

ONGOING

BOSA acceptance

OCTOBER

verify that the outcomes of the previous phases meet the expectations

scheduled

...

Hermes agreements framework

...