Could it be that it does not pass the token validation https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/validation/DeviceTokenValidator.java#L35 ? 

On Fri, Apr 15, 2016 at 4:07 PM, ffraticelli <ffraticelli@unog.ch> wrote:
Hello, I found this (blocking) issue using the REST API for registering devices. It's a test container, you can use the commands below and I will delete the variant once this issue is confirmed by your team. The following curl works and registers the device token: curl -u "daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40" \ -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid" \ -X POST -d \ '{ "deviceToken" : "fffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd", "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2" }' \ https://aerogear-unog.rhcloud.com/ag-push/rest/registry/device While the following receives an HTTP 400 Bad Request. The only different between the 2 is an additional 'f' in the following token. curl -u "daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40" \ -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid" \ -X POST -d \ '{ "deviceToken" : "ffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd", "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2" }' \ https://aerogear-unog.rhcloud.com/ag-push/rest/registry/device With the actual token (without the f list) t doesn't work either, 400 error.
View this message in context: bug (?) in the REST API
Sent from the aerogear-users mailing list archive at Nabble.com.

_______________________________________________
Aerogear-users mailing list
Aerogear-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users