You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requests using the API fail when using the apiKey for authN/Z. This was caused by the upgrade to Play 2.9 because the Play Application secret was also (and unknowingly) used on the backend's side for encrypting certain backend-private data.
An example API call using the apiKey header:
curl -H "apiKey:<TODO_APIKEY>" -X GET https://maproulette.org/api/v2/user/whoami | jq
The text was updated successfully, but these errors were encountered:
The resolution is described in #1128 : Play 2.9 introduced a change where its application key must be 32 bytes or longer, and this impacted MapRoulette's cryptography with its own internal items. It's easier to manage these separately, similar to how the OSM secrets are not used to encrypt data stored within MapRoulette.
Requests using the API fail when using the apiKey for authN/Z. This was caused by the upgrade to Play 2.9 because the Play Application secret was also (and unknowingly) used on the backend's side for encrypting certain backend-private data.
An example API call using the apiKey header:
The text was updated successfully, but these errors were encountered: