05-06-2010 08:53 AM
It's not the portal username and password you want to use to push. Those credentials are used to login to the RIM hosted administration website where you can manage your push application attributes.
In the content of entering your push application details in the DebugPortal, the Id and Username fields will be the same value - namely the Application Id you got in the email from RIM. It just so happens the application ID and username are the same values in BIS push; they can be different for BES push hence the two different form fields in the DebugPortal. And the password to use is the Pwd: not the Portal Pwd:. Again the Portal Pwd: is used to login to the RIM hosted admin pages.
If you are using the right username and password the next thing you need to make sure is the IP of the server you are pushing from is the IP RIM has registered for you.
Hope that helps.
05-06-2010 02:17 PM - edited 05-06-2010 02:18 PM
05-06-2010 04:04 PM
Looks like you setup the Push Application correctly in the Debug Portal. One thing I want to confirm the password you used is the Password: field under the 'Server' category of the email, right? Ensure you are *not* using the Portal Pwd:. And application id should be of the from xxx-xxxxxxxxxxx (alpha numeric)
When you pushed the push id should be some random alpha numeric string (you can leave it blank and the SDK will autogenerate one for you). It is not the name you used when invoking registration in the client application. The name you used when you invoked the registration in the client application becomes your "subscriber id". When you push you can then push to your subscriber id or in your case you did a 'push_all' which works too. Either way that won't cause you Unauthorized error.
I am not sure about the NAT router. Ultimately, you need to find out what your IP is when it arrives at the RIM push infrastructure. That IP must match the Source IP: field in the registration confirmation email RIM sent you. I don't believe there is any trickery with the HTTP header.
05-06-2010 04:41 PM
> One thing I want to confirm the password you used is the Password: field under the 'Server' category of the email, right?
> Ultimately, you need to find out what your IP is when it arrives at the RIM push infrastructure.
I have no way of viewing logs from RIM push infrastructure.
I can only do the following check: visit
using a Web browser on the same machine, where I run BB Push application.
Your IP Address is: xx.xx.xx.xx
Which is exactly the same IP address as "Source IP" in my BB Push registration E-Mail.
May be HTTPS has some different behavior from HTTP, like client authentication? Just guessing.
05-07-2010 10:57 AM
Sorry I can't help you more. Sounds like you need someone from RIM to help you investigate further what is wrong. They can probably check logs on their side to give you more info. I wonder if someone here knows who to email for help.
05-10-2010 03:57 PM
I understand that RIM assign the port to each application. Do I need to specifiy the port in my server application? If I do, how? Thanks.
05-11-2010 10:29 AM
Yes, port is assigned by RIM. The port is really only required for your device side application so it knows what port to listen on for pushed messages.
The server side application does not need the port number. The SDK keeps that information for archive/read-only purposes only so if you ever forget what port RIM assigned you it is kept somewehre in electronic persistent storage.
06-18-2010 03:12 AM
Am facing the same problem. The Unauthorized exception. If some one over here sorted it out please let me know.
I confirmed am using the correct username and password. And also my ip is correctly registered with eval system.
Thanks in Advance
08-03-2010 04:30 PM
Just wanted to followup to mdicesare's post as it was very helpful in getting our standalone implementation working. That sample code should have been part of the official documentation! As another forum post I read pointed out, the papnotify sample does not come with source.
It seems that PushSDKPropertiesImpl() requires that the PushSDK.properties file be in the classpath, so make sure you include that in your web application's WAR file. What I did was override the values at runtime like this:
PushSDKPropertiesImpl properties = new PushSDKPropertiesImpl();
01-14-2011 05:23 PM
Hi I am new to blackberry development. Can you please share me the server and client code for Blackberry push notification? I have done for Android and Blackberry. Trying for Blackberry now. Planing to do for Windows Mobile as well in near feature.
Please help me for this. Thanks in Advance.