[aerogear-dev] Allow Push Without Master-Secret?

Hey there guys! We are currently working on our semester project which allows you to sync notifications across different devices. The notifications themselves are stored on a separate webserver, but we are using the aerogear unified pushserver to start a sync. All the devices which should receive the push (and start the sync) are using the same alias, the push will be triggered by one of these devices On Android it should work fine, since we are able to use the Java Client and the secret without a problem (at least i think the secret would not be visible to anyone on Android). But we are also planning to implement a Chrome Addon and we don't really like the idea to make the master-secret visible to everyone. We know that the unified push server is not intended to be used as client-to-client push server atm, but since the pushes don't contain any important data it would be a sufficient solution to just disable the need for a master-secret if an alias is given (this would at least prevent broadcasts from being sent by third persons). So we wanted to ask you guys which lines of code we should modify inorder to allow pushes without master-secret, if an alias is given? It should only be an additional "if", I guess.. or does it get more complicated? We are currently hosting our unified pushserver on OpenShift (would be nice if you could also roughly tell us how to push the changes onto the server.. do we need to recompile everything?) Cheers, Florian -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Allow-Push-Without... Sent from the aerogear-dev mailing list archive at Nabble.com.