Zendesk.initialize(appId: "1e41a02a5f85d58e009ed4fa", clientId: "mobile_sdk_client_e1c4e6262f1d02f43496",zendeskUrl: "https://omniwear.zendesk.com");
let token = Identity.createJwt(token: "unique_db_user_identifier")
Zendesk.instance?.setIdentity(token)

let helpCenter = HelpCenterUi.buildHelpCenterOverviewUi(withConfigs: [])
navigationController?.pushViewController(helpCenter, animated: true)

[DEBUG]: Returning cached settings for HelpCenterSettings.Type
[INFO]: Localization key and value : "ios.ZDKHelpCenter.helpCenterOverview.title" = "Help";
[DEBUG]: Reachability Flag Status: -R ------- networkStatusForFlags
[DEBUG]: Returning cached settings for ConversationsSettings.Type
[DEBUG]: Returning cached settings for HelpCenterSettings.Type
[INFO]: Localization key and value : "ios.ZDKHelpCenter.support.contactSupport" = "Contact us";
[INFO]: Localization key and value : "ios.ZDKHelpCenter.support.contactSupport" = "Contact us";
[DEBUG]: Returning cached settings for HelpCenterSettings.Type
[DEBUG]: Returning cached settings for HelpCenterSettings.Type
[DEBUG]: Returning cached settings for CoreSettings.Type
[ERROR]: Login error : Error Domain=com.zendesk.sdk.core Code=1000 "unauthorized" UserInfo={error=Couldn't authenticate you, HTTP Status code=401, NSLocalizedDescription=unauthorized}
[INFO]: Localization key and value : "ios.ZDKHelpCenter.support.contactError" = "Unable to connect";
[INFO]: Localization key and value : "ios.ZDKHelpCenter.toastRetryButton" = "Retry"

curl "https://<domain>/admin/zendesk/jwt" -d "user_token=harigharan.e@gmail.com" -v -X POST
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying …..
* Connected to … port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=..
*  start date: Jan 18 01:42:49 2022 GMT
*  expire date: Apr 18 01:42:48 2022 GMT
*  subjectAltName: host “..” matched cert's “..”
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
> POST /admin/zendesk/jwt HTTP/1.1
> Host:..
> User-Agent: curl/7.77.0
> Accept: */*
> Content-Length: 33
> Content-Type: application/x-www-form-urlencoded
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx/1.18.0 (Ubuntu)
< Date: Fri, 18 Feb 2022 15:27:09 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 211
< Connection: keep-alive
< Content-Security-Policy: default-src 'self';base-uri 'self';block-all-mixed-content;font-src 'self' https: data:;frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
< X-DNS-Prefetch-Control: off
< Expect-CT: max-age=0
< X-Frame-Options: SAMEORIGIN
< Strict-Transport-Security: max-age=15552000; includeSubDomains
< X-Download-Options: noopen
< X-Content-Type-Options: nosniff
< X-Permitted-Cross-Domain-Policies: none
< Referrer-Policy: no-referrer
< X-XSS-Protection: 0
< Access-Control-Allow-Origin: *
< ETag: W/"d3-ECX7al3yFow40Aa+HPqwW9dVYq8"
< Vary: Accept-Encoding
< 
* Connection #0 to host  left intact
{"jwt":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJlbWFpbCI6ImhhcmlnaGFyYW4uZUBnbWFpbC5jb20iLCJuYW1lIjoiSGFyaWdoYXJhbiBFIiwiaWF0IjoxNjQ1MTk4MDI5LCJleHAiOjE2NDUyODQ0Mjl9.tNxFRnm0Gv9NTFPXQhAcOCk3oHECZbsWW-GEe__RSKs"}

  - ZendeskChatProvidersSDK (2.11.1)
  - ZendeskChatSDK (2.11.1):
    - ZendeskChatProvidersSDK (~> 2.11.1)
    - ZendeskMessagingSDK (~> 3.8.2)
  - ZendeskCommonUISDK (6.1.1)
  - ZendeskCoreSDK (2.5.1)
  - ZendeskMessagingAPISDK (3.8.2):
    - ZendeskSDKConfigurationsSDK (~> 1.1.8)
  - ZendeskMessagingSDK (3.8.2):
    - ZendeskCommonUISDK (~> 6.1.1)
    - ZendeskMessagingAPISDK (~> 3.8.2)
  - ZendeskSDKConfigurationsSDK (1.1.8)
  - ZendeskSupportProvidersSDK (5.3.0):
    - ZendeskCoreSDK (~> 2.5.1)
  - ZendeskSupportSDK (5.3.0):
    - ZendeskMessagingSDK (~> 3.8.2)
    - ZendeskSupportProvidersSDK (~> 5.3.0)

• Mick O'Donnell

  • 23 février 2022 13:39

  Zendesk Product Manager

  Hi Harigharan,
  
  Thanks for reaching out. I don't see anything obviously wrong with this implementation. I'll turn this post into a Support ticket, and we'll take a closer look.

• Harigharan E

  • 23 février 2022 15:06

  Thanks, Mick O'Donnell. Let us know once you got any updates on this ticket.

• Ashrith

  • 27 mai 2022 13:21

  Any updates on this ticket or any links to the support ticket created?

• Kamran Manzoor

  • 7 juillet 2023 11:04

  Mick O'Donnell Can you please update us? On android application it's not working too

• Mick O'Donnell

  • 10 juillet 2023 12:40

  Zendesk Product Manager

  In this case, there was an issue with Harigharan's implement, and we were able to help support them via a Support ticket. We link to link to private support tickets on this public forum, sorry. If you're having difficulty with an integration, I advise you to open a respective support ticket with Zendesk Support and we can assist you.

• Muhammad Waris Shams

  • 10 juillet 2023 17:57

  Hi Mick O'Donnell we already open a ticket and didn't get helpful response. 
  Here is the ticket link can you please look.

  Thanks.

• Taimoor Saleem

  • 27 juillet 2023 07:56
  • Modifié

  The jit key is missing in the JWT payload. It will not work if any of these keys are missing.
  JWT Payload documentation

Vous devez vous connecter pour laisser un commentaire.