Question

Native iOS App Login Issue - Operation failed with HTTP status 403.","code":7

Issue:

Upon logging in on the Native iOS app, an error 403 (code 7) occurs.

Logging in a second time, is succesful.

Also:

  • Access group - Offline enabled
  • Case - Offline enabled

Log file (last lines):

7/9/2019, 8:05:59 PM|INFO|com.pega.hybridclient.bootstrap|JS: Info :: Application 'https://XXX' installation progress: 90%
7/9/2019, 8:06:00 PM|DEBUG||Installation progress changed: 94% for [https://XXX].
7/9/2019, 8:06:00 PM|INFO||Installation failed for [https://XXX] with error [Operation failed with HTTP status 403.].
7/9/2019, 8:06:00 PM|INFO|com.pega.hybridclient.bootstrap|JS: Info :: Application 'https://XXX' installation progress: 94%
7/9/2019, 8:06:00 PM|INFO|com.pega.hybridclient.bootstrap|JS: Info :: Application 'XXX.APP' has changed status from 'installing' to 'failed'. With error : {"description":"Operation failed with HTTP status 403.","code":7}
7/9/2019, 8:06:00 PM|INFO|com.pega.hybridclient.bootstrap|JS: Error :: application installation has failed. Due to : {"description":"Operation failed with HTTP status 403.","code":7}
7/9/2019, 8:06:00 PM|INFO|com.pega.hybridclient.bootstrap|JS: Info :: Synchronization idle - closing account...
7/9/2019, 8:06:00 PM|INFO|com.pega.hybridclient.bootstrap|JS: Info :: AccountManager account will be closed.
7/9/2019, 8:06:00 PM|DEBUG||Unregister subscriber
7/9/2019, 8:06:00 PM|INFO|com.pega.hybridclient.bootstrap|JS: Success :: Logged out 'XXX.USER' user

Comments

Keep up to date on this post and subscribe to comments

Pega
August 16, 2019 - 12:11pm

Hi Bob!

It would appear that one of the HTTP handshakes with the server failed during initial startup.  HTTP 403 would indicate that the server rejected the connection.  Depending on how you configured your authentication for the servlet and for the service package OfflineHTTP, there may be an issue with the Pega-RULES cookie not getting established correctly on the first try.  Or, you may need to upgrade to a newer version of the Pega Mobile Client.  Or, when the app tries to synchronize, the load balancer might have lost affinity.

What version of Pega are you using?

What version of the Pega Mobile Client are you using?

How have you configured the authentication service for your servlet and for offline http?

What load balancer are you using and how are you controlling affinity?

Can you capture HTTP traffic during login with Fiddler, Charles or WIreshark and verify the cookies in the HTTP header are correct?

- James