3

to send a GCM, we have a SENDER ID from Google API console, is that important to keep that SENDER ID protected? I mean, would someone be able to do bad things if they know that ID? I did a mistake and I think that ID was in one of my projects... am I able to somehow change it? I couldn't find anyway to change it by looking at the Google API console!. should I be worried about that? or is it ok?

the server and browser API keys can be changed but not the SENDER ID, PROJECT NUMBER...

Eran
  • 387,369
  • 54
  • 702
  • 768
Hadi tavakoli
  • 1,267
  • 2
  • 16
  • 30

3 Answers3

5

Yes you should keep the project number (which is the Sender Id as well for GCM) protected; otherwise anyone can use it and it will count toward your usage of the API. It is similar to the API key for any other service e.g. Google Maps.

I am not aware of any method to change it other than create a new Google account, but in the Dashboard of Google API console there is an option to register/generate a Project ID but I am not sure if GCM will accept this as Sender Id. You can give it a try.

Edit:

It might not be that dangerous if your project number is exposed (in the old APIs the sender id was your e-mail) , because still you will need API key to be able to send notification via GCM

iTech
  • 18,192
  • 4
  • 57
  • 80
  • 1
    iTech, thanks for you reply but as far as I tested, a SENDER ID won't work if you don't know the SERVER API KEY. so, if I keep the server api key protected, would that be still a problem? – Hadi tavakoli Feb 09 '13 at 07:06
  • Yes, you are right. Both are needed to be able to send messages via GCM – iTech Feb 09 '13 at 07:12
2

I'd like to add that while project ID alone can't be used to send notifications via GCM, it can be used by another Android application to register to GCM and recieve notifications from your server. Of course, in order to recieve notifications from your server, that application would have to first contact your server to send its Registration Id, so depending on the server implementation, you can block that from happening.

Eran
  • 387,369
  • 54
  • 702
  • 768
0

As I understand it:

1) SenderID == ProjectID (as iTech notes)

2) The SenderID/ProjectID is embedded into your app, at build time, via "googleservices.json"

3) Your app uses & requires your SenderID (via R.string.gcm_defaultSenderId) to register with GCM, using the following code:

String token = instanceID.getToken(getString(R.string.gcm_defaultSenderId), GoogleCloudMessaging.INSTANCE_ID_SCOPE, null);

4) Thus, as per my understanding, it is by design that SenderID should be included in your GCM app, and is not protected.

Mtl Dev
  • 1,604
  • 20
  • 29