Versions Compared

Old Version 16

changes.mady.by.user Laurent KLOETZER

Saved on

compared with

New Version Current

changes.mady.by.user Laurent KLOETZER

Saved on

Key

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

Due to the difficulty and integration and support pain, this interface must not be deployed anymore, until it has been entirely rewritten.

Please contact LKL for any question.


What is Otipass?

The digital passport of your territory Otipass proposes innumerous territories ( Paris Jerusalem Nantes Reims Bordeaux Lille Grenoble Côte d'Azur Villeneuve Nancy Mulhouse Alsace Dijon) digital passes to visit freely the most beautiful local sites. Every Pass is a real good plan: you benefit from a free entrance to each of the partner sites.

...

  1. In Institution menu / Organisations / open the access control parameters of the organization and check that the version of the APÏ used is 1.4+
  2. In Organization/Access control/External interfaces, create a new Otipass interface, containing the setup information received from Otipass
    • Interface Type: OTIPASS
    • URL, Username, Password information will be provided by the Otipass system
    Open a ENV JIRA to ask
    • as an api Key

Ask that the Otipass url is added to the autorizations in the proxy for tnac.

  • Mapping Parameters
    • Otipass information: SectorCode has to be defined in the mapping with the Otipass SpaceID.
    • SecuTix information: SeasonCode and ProductCode are mandatory to create Sales in SecuTix.


Note

Common problems

  • The URL entered must end by /api. If Otipass provided a different url, like: https://otipass.net/api/toulouse, the part in bold must be removed and entered in the json as OtipassProjectId
  • Check that the JSON  syntax is correct (for example using https://jsonlint.com/)
  • The screen of external interfaces of tnac is buggy. It will remove the password each time you save. So you have to manually add everytime you do any change.





Here you can download a correct reference mappings parameter.

Example: (do not copy-paste it. And if you take an inspiration of it, do not forget to remove the //comments)

Code Block
{
   
   "OtipassProjectId":"toulouse", //The project id of Otipass. It is generally the last part of the url that they provide.
   "NumType":"serial", //define this value if the pass codes start with letters
   "sectorInfos":{
      "DDMM_AUG":{ //This is the sector code as defined in TNAC configuration.
         "OtipassServiceId":"pcumid031fs00061", //Provided by Otipass
         "OtipassPSpaceId":"PROVIDER#PCUMID031FS00061", //Provided by Otipass
         "seasonCode":"DDMM23", //Those are the season and product codes on which the sales will be processed.
         "productCode":"PASSTOU"
      },
      "DDMM_MSR":{
         "OtipassServiceId":"PCUMID031FS00071",
         "OtipassPSpaceId":"PROVIDER#PCUMID031FS00071",
         "seasonCode":"DDMM23",
         "productCode":"PASSTOU"
      },
      "DMM_DUP":{
         "OtipassServiceId":"PCUMID031FS0006E",
         "OtipassPSpaceId":"PROVIDER#PCUMID031FS0006E",
         "seasonCode":"DDMM23",
         "productCode":"PASSTOU"
      }
   }
}


Note

Beware of the following two points:

  • In the parameters, a given sector code can only appear once.
  • The device scanning Otipass tickets must be linked to a door which must be associated to only one sector.

Scanning Otipass cards

There are two steps to the scanning:

...