Versions Compared

Key

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

Introduction

During the transition there are 2 major work blocks: changing the authentication and switching to the renewed GIPOD API. 

The renewed GIPOD API ( gipod.api.vlaanderen.be ) will work with both Geosecure and ACM authentication, but the existing GIPOD API ( private-api.gipod.vlaanderen.be ) will only work with Geosecure authentication.

Therefore we recommend switching to the renewed API & changing the authentication in one go.

TL;DR for CCG with JWK

Beta

Production

  1. Validate in Beheerportaal T&I that your existing client was successfully migrated to ACM, and remember the new client id.

  2. Adapt oauth access token request information and update oauth URLs from beta.oauth.vlaanderen.be/... to authenticatie-ti.vlaanderen.be/... using the

...

  1. client id from step 1.

  2. Update GIPOD API endpoint from private-api.gipod.beta-vlaanderen.be to gipod.api.beta-vlaanderen.be

  3. Validate that your existing client

...

  1. works with the new endpoints

...

  1. and authentication mechanism

  1. Validate in Beheerportaal that your existing client was successfully migrated to ACM, and remember the new client id.

  2. Adapt oauth access token request information and update oauth URLs from oauth.vlaanderen.be/... to authenticatie.vlaanderen.be/... using the

...

  1. client id from step 1.

  2. Update GIPOD API endpoint from private-api.gipod.vlaanderen.be to gipod.api.vlaanderen.be

  3. Validate that your existing client

...

  1. works with the new endpoints

...

Introduction

...

  1. and

...

The renewed GIPOD API ( gipod.api.vlaanderen.be ) will work with both Geosecure and ACM authentication, but the existing GIPOD API ( private-api.gipod.vlaanderen.be ) will only work with Geosecure authentication.

...

  1. authentication mechanism

Set up clients in ACM 

The current Geosecure clients are being phased out. 

...