Authorization headers

Each request message from a content provider starts with an authorization header that identifies the content provider. You must create the authorization with the basic access authentication procedure for messages sent by HTTPs. The basic access authentication procedure concatenates a user name, a colon, and a password and then encodes the string with the Base64 algorithm.

The Push Service uses the basic access authentication procedure but different values for the user name and password, with the values that are provided in the registration email from RIM as follows:
  • For the user name, the Push Service uses the App ID field in the registration email (application ID).
  • For the password, the Push Service uses the Pwd field in the registration email (password).

Example: The authorization header of a request message

Authorization: Basic QVxhZHRpbgpvcGWuIHNlc2FtZQ==


Was this information helpful? Send us your comments.