Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As a complement to BoB Tech we have BoB Tech Live. That’s a live meeting to be able to discuss more effective. All members of BoB Tech are invited and everyone can suggest topics to discuss. It’s a Skype meeting but you can always participate at Samtrafiken in person if you prefer that. The meeting is held at least 4 times a year.

Test Environment for Servers

A set of scripts to test BoB server implementations can be found at https://bitbucket.org/samtrafiken/bobby .

Test Environment for Clients

Host

https://bobby.samtrafiken.se/api/v1

Access

To request access to the test environment, please submit the following information to bobsupport@samtrafiken.se:

  • Name

  • Affiliation

  • Email address

  • BoB AuthZ Group Requested

    • VAL = Validator

    • INS = Inspector

    • TVM = Ticket Vending Machine

    • POS = Point of Sale

    • APP = Application Backend (for requesting application keys)

    • TEST = Test (all of the above)

  • SHA1 fingerprint of self-signed certificate

Certificate Generation

To generate a self-signed certificate and show the SHA1 fingerprint using OpenSSL, you should use the following commands:

openssl req -new -x509 -sha256 -days 1000 \
    -newkey rsa:2048 -nodes -keyout bobby.key \
    -subj "/CN=Name" -out bobby.crt
openssl x509 -noout -fingerprint -in bobby.crt

...

Samtrafiken has developed a Docker Image of the Participant Metadata service to enable isolated interoperability testing between participants during implementation development. If you have several integrations ongoing you can run multiple instances of the Docker Image.

...

If you want to use the BoB Metadata Docker Image write an e-mail to bobsupport@samtrafiken.se

To be able to run the BoB Metadata Docker Image you need to have this in place:

  • Docker

  • MS SQL Server (including a database user and an empty database)

  • Unique Participant Metadata Public Key for each participant generated according to MTS 5 section 3.1 and registered in the database (Docker Image).