nerdexam
Cisco

300-810 · Question #21

Refer to the exhibit. Apple Push Notification integration is configured in a Cisco Unified IM and Presence deployment and has been working property. Administrators now report the error "Push…

The correct answer is D. Update Refresh Token Manually. Apple Push Notification Service (APNS) integration with Cisco IM&P uses OAuth 2.0 tokens (specifically a Refresh Token) to authenticate with Apple's cloud infrastructure. These refresh tokens have a limited validity period. When the token expires, subsequent API requests to…

Cisco Unified IM and Presence and Cloud Messaging

Question

Refer to the exhibit. Apple Push Notification integration is configured in a Cisco Unified IM and Presence deployment and has been working property. Administrators now report the error "Push notification settings cannot be configured. 400 Bad Request." in the GUI, and HTTP logs are displaying the errors that are shown in the exhibit. Which action solves this issue?

Exhibit

300-810 question #21 exhibit

Options

  • AFix the network connectivity to Apple iCloud.
  • BReboot the IM&P cluster.
  • CChange the HTTP proxy settings to remove errors in request syntax.
  • DUpdate Refresh Token Manually.

How the community answered

(57 responses)
  • A
    2% (1)
  • B
    5% (3)
  • C
    11% (6)
  • D
    82% (47)

Explanation

Apple Push Notification Service (APNS) integration with Cisco IM&P uses OAuth 2.0 tokens (specifically a Refresh Token) to authenticate with Apple's cloud infrastructure. These refresh tokens have a limited validity period. When the token expires, subsequent API requests to Apple's servers fail with a '400 Bad Request' error because the authentication credentials are no longer valid. The solution is to manually update/renew the Refresh Token in the IM&P administration GUI under Push Notification settings. Option A (network connectivity to Apple iCloud) would result in connection timeout errors, not a 400 status code. Option B (rebooting the cluster) does not address an expired token. Option C (HTTP proxy settings) would cause a different type of error related to proxy misconfiguration, not a 400 from Apple's API indicating an invalid/expired token.

Topics

#Apple Push Notification#Cisco Unified IM and Presence#Troubleshooting#Refresh Token

Community Discussion

No community discussion yet for this question.

Full 300-810 Practice