The mailing list for users of the eduroam Configuration Assistant Tool (CAT)

[Martin Božič <martin.bozic AT arnes.si>]

Hello!

At Arnes we are having an urgent issue. We're in the middle of a massive
Eduroam deployment in elementary and high schools and we're using
cat.eduroam.org API in our home grown self-service provisoning portal which
orchestrates the FreeRADIUS, LDAP and DHCP and CAT portal and profiles 
provisoning.

It seems that that todays update of cat.eduroam.org API broke out
provisioning system. This is what we've found out so far:

- [just for context] on 3.10.2018 we've resolved an internal issue with 
  on provisioning system with a simple workaround, and deployed on production
  in the late afternoon.
- the last succesful provisoning by our system was completed yesterday
  morning (3.10.2018)
- the error that we've got from debugging the self-service provisioning
  portal is the following:

   - API endpoint our portal is calling: https://cat.eduroam.org/admin/API.php
   - debug from example payload (note that this is Python output which is not
     in valid JSON format):

     {
        'option[S90]': 'profile-api:eaptype',
        'option[S3]': 'eap:ca_url',
        'option[S1]': 'general:instname',
        'value[S1-0]': u'OSNOVNA \u0160OLA MUTA',
        'option[S5]': 'eap:server_name',
        'value[S69-3]': 'on',
        'option[S66]': 'profile:name',
        'value[S4-0]': '',
        'APIKEY': 'a******************f',
        'NEWINST_PRIMARYADMIN': '',
        'value[S4-lang]': 'C',
        'ACTION': 'NEWINST',
        'value[S90-0]': 1,
        'option[S70]': 'profile-api:realm',
        'option[S69]': 'profile:production',
        'value[S66-0]': u'OSNOVNA \u0160OLA MUTA',
        'option[S4]': 'support:email',
        'value[S3-0]': 
'ftp://ftp.arnes.si/software/eduroam/arnes_eduroam_ca_2012.pem',
        'option[S72]': 'profile-api:anon',
        'value[S67-1]': u'Profil za uporabnike organizacije: OSNOVNA 
\u0160OLA MUTA',
        'option[S91]': 'profile-api:eaptype',
        'option[S67]': 'profile:description',
        'value[S70-0]': u'osmuta.si',
        'value[S5-0]': 'orle.arnes.si',
        'value[S71-3]': 'on',
        'value[S91-0]': 2,
        'value[S72-0]': u' AT osmuta.si',
        'value[S66-lang]': 'C',
        'option[S71]': 'profile-api:useanon',
        'value[S1-lang]': 'C'
     }

   - response from cat.eduroam.org API:

     {
        "result": "ERROR",
        "details": {
            "errorcode": 8,
            "description": "Unable to decode JSON POST data."
       }
     }

- our testing environment where we use API from
  https://cat-test.eduroam.org/branch/admin/API.php is doing fine.


Unfortunately, since the hand-off from the original AAI/developer team that
developed our portal somehow missed this detail on so strictly relying
on cat.eduroam.org API, we weren't aware and ready of the coming CAT upgrade.
That's why we're now in a showstopper situation and unable to meet our 
deployment deadline, thus jeopardizing the project. We can't afford to
workaround with excluding the CAT from our provisioning system because
it's actually a cornerstone of the rollout.

We're asking for help or any information about API changes that could
help us restore the service as soon as possible.

Regards,
Martin Božič