Let's wait for Matzew to confirm but I think you can ignore it. Looks like a left over from our first analytics implementation , we use now a separate endpoint (the PUT) and pass this ID as a path parameter.is it something specific, or just a random number/alpha-numeric thingythats right folks, i'm asking this question on a Friday before a Holiday weekend(US) at 3:52(est)i've started to implement the Device registration endpoints in node and was just wondering what the id is here in this header-v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid"here is the doc link for reference: https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932
Make sense , I like thatI've also decided to create this as a separate module instead of including it in the node admin client here: https://github.com/bucharest-gold/unifiedpush-admin-clientmostly becuase these registration endpoints don't needed to be KC authenticated. and they could also be used on a IOT device or something that runs node that has webpush/simplePush or some new crazy protocol.
-Luke
_______________________________________________
Aerogear-users mailing list
Aerogear-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users