最近搜索
没有最近搜索

Marco
已加入2021年10月29日
·
最后活动2025年1月23日
关注
0
关注者
0
活动总数
72
投票
19
订阅
21
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Marco
Marco 创建了一个帖子,
Hello!
We're experiencing an issue with Clipboard copy from our ZAF application which is located in the left navigation bar, as per manifest.json:
...
"signedUrls": true,
"location": {
"support": {
"nav_bar": {
"url": "...",
"flexible": true
}
}
},
...
Our app is firing an error on attempting to copy any text to the clipboard:
[Violation] Permissions policy violation: The Clipboard API has been blocked because of a permissions policy applied to the current document.
It turns out that any ZAF application is automatically placed by Zendesk inside an
We use standard code to fill-in the clipboard:
navigator.clipboard.writeText("string"))
see doc here:
https://developer.mozilla.org/en-US/docs/Web/API/Clipboard/writeText
Also, please note that we already created a ticket to Zendesk (#12790398), and here is their feedback:
...After reviewing the information that you provided, I wanted to put you in contact with our Developer Support team. They have more in-depth knowledge of our platform tools and will be able to get you the best possible answers and solutions. This team works out of our Developer Support community, which will also give you the opportunity to have other developers to share their insight as well!
Thanks for any help!
Marco
已于 2024年8月30日 发布 · Marco
0
关注者
0
投票
0
评论
Marco 进行了评论,
@Cathy L
what about this EAP? We're in Q2 now
>1. We are currently working on a capability to enable admins to associate custom statuses with individual ticket forms, which will be the first step toward providing a shorter, relevant list of statuses to agents in the ticket status picker. We're targeting a closed EAP in Q1 2024.
查看评论 · 已于 2024年4月09日 发布 · Marco
0
关注者
0
投票
0
评论
Marco 创建了一个帖子,
I created a support ticket for Zendesk, but they asked me to post the issue here.
LIMITATION:
Our agents are not alerted (in their side-conversation emails) when target email has errors like this one (or similar):
Error "550 5.1.1 User Unknown
In other words, it seems that Zendesk is filtering-out these errors, and this is NOT good for our workflows. As there is no reply, the ticket will remain in PENDING status forever instead of returning to OPEN status with error clearly reported!
And, here is the ANSWER from Zendesk:
Our dev team had replied to our question internally and confirmed it is expected, currently we have a limitation and those responses are not added to side conversations. Devs are internally chatting about it, but a solution is not yet in the roadmap.
---
Thanks,
Marco
已于 2024年3月19日 发布 · Marco
4
关注者
3
投票
2
评论
Marco 进行了评论,
Quang Cao try to decode the jwt here.. https://jwt.io/
If the token is valid (assuming not expired), you should see header and payload on the right side of the screen..
查看评论 · 已于 2024年2月28日 发布 · Marco
0
关注者
0
投票
0
评论
Marco 进行了评论,
+1
@Zendesk
In addition to what is planned for Q1 2024 consisting in associate custom statuses with individual ticket forms (which is very useful!), we also propose a different approach that is more "workflow-oriented".
You can define custom statuses which may be NOT segregated by form or group. Conversely they're driven by a statuses-based workflow.
In other words, a custom status is NOT proposed/allowed if it is incompatible with current ticket status. This is similar to the workflows that you can actually define in JIRA.
Thanks.
查看评论 · 已于 2024年2月22日 发布 · Marco
0
关注者
0
投票
0
评论
Marco 进行了评论,
Hi,
I also need to setup SLA policies for API created tickets.
API created ticket implies that it's created by an agent (eg. via API Token). So, I wonder if I can still measure First Reply Time for that case? If not, which is the best metric available for API created tickets, to measure the responsiveness?
查看评论 · 已于 2024年2月08日 发布 · Marco
0
关注者
0
投票
0
评论
Marco 进行了评论,
I did a try the new procedure based on the (updated) examples you posted on the github. I was able to get it to work... however something is not quite right in my understanding...
With the deprecated method (valid until May 2024).. I could run all code on backend side in order to:
1. generate jwt string
2. build sso redirect url including return_to url
3. finally redirect to Zendesk
eg. (in Python/Flask)
jwt_string = jwt.encode(payload, ZENDESK_JWT_SSO_SECRET)
sso_url = "https://SUBDOMAIN.zendesk.com/access/jwt?jwt=" + jwt_string + "&return_to=..."
return redirect(sso_url)
With the new method, all code have to be run inside the user’s browser as html/javascript code, including the Ajax call that is needed to get the jwt string from our backend (BTW: how to authenticate that ajax call?!?)
I think something is still not clear to me... where is the value added?
--- EDIT (2024 Jan 8th)
in order to avoid the ajax call from the browser.. i think all the javascript code can be dynamically generated from the back-end as follows:
jwt_string = jwt.encode(payload, ZENDESK_JWT_SSO_SECRET, algorithm="HS256", headers={"typ": "JWT"})"
action_url = "https://SUBDOMAIN.zendesk.com/access/jwt?return_to=..."
sso_page = (
'
+ ''
)
return sso_page
As I stated earlier, I don't like this solution.. but it works without a great impact. Also, I added one javascript line to automatically submit the FORM data as soon as the page is fully loaded.. Hope this helps.
查看评论 · 已于 2024年1月08日 编辑 · Marco
0
关注者
5
投票
0
评论
Marco 进行了评论,
What??? We're not aware of any change in the SSO authentication method.. and we're NOT ready to change its implementation.
Basically, our backends redirect the user to this URL:
https://.zendesk.com/access/jwt?jwt=...&return_to=
where ... = encoded payload..
If this stops to work next year then we'll be lost!
查看评论 · 已于 2023年12月15日 编辑 · Marco
0
关注者
1
投票
0
评论
Marco 进行了评论,
@ Chris
I think the answer is YES to both questions one and two. The big issue with Zendesk is that you have one single User Registry and one single Authentication status for the whole account. So, if you log into Zendesk via the Brand 2, you are automatically logged in Brand 1 as well. It doesn't matter if you're logged in via SSO or not, you are just authenticated, stop!
The only work-around I see is to restrict access to HelpCenters based on Users/Organizations tags (Users segmentation).
Let's hope to get some better official answer from Zendesk...
查看评论 · 已于 2023年11月14日 发布 · Marco
0
关注者
0
投票
0
评论