Pesquisas recentes
Sem pesquisas recentes

Stephen Barbarino
Entrou em 16 de ago. de 2022
·
Última atividade em 04 de mar. de 2024
Seguindo
0
Seguidores
0
Atividade total
16
Votos
1
Assinaturas
7
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Stephen Barbarino
Stephen Barbarino comentou,
Melissa, I'm not with Zendesk but what you described is how I fixed it in my environment. I removed first name from the SAML attribute map which stopped it from updating the name field whenever a user with a preferred name authenticated into the app. Just be warned, every environment is different so you should 100% test this before rolling it out to production. We use UPNs as unique keys Zendesk which is why we were able to remove first name safely. I did keep last name in there though.
I hope that helps.
Exibir comentário · Publicado 04 de mar. de 2024 · Stephen Barbarino
0
Seguidores
0
Votos
0
Comentários
Stephen Barbarino comentou,
For those of you struggling with this, let me provide the detail that Zendesk support should have provided instead of just saying "it's SSO".
If you are mapping a display name to first name in Zendesk using SCIM when provisioning users, you'll notice that the first name of the user in Zendesk will update. This is great, it's what most of us want.
Here comes the issue : When the user logs in via SSO, your SAML attribute mapping is overwriting the name with whatever name field is mapped to first name, that's why it's updating the users name.
Take a look at your SAML attribute claims in your SSO configuration in your identity provider (Azure AD in my case) for Zendesk, that's where you'll see where you need to make the update. The default claims maps givenName in azure to first name in Zendesk. I can't tell you how to fix this but this at least gives you some direction in how to get this solved. If you're not responsible for your identity provider configuration, this information should at least point those that are in the correct direction for a solution. In my case, since I'm using Azure AD, I was able to adjust the default claims to stop SAML from updating our users first name when they log in.
Zendesk support, it really wouldn't have killed you guys to provide a bit more information other than "it's SSO" especially when so many of us already told you we were provisioning users from the same identity provider that we're using for SSO. This is totally fixable in most IdP's.
Hope this info helps.
Exibir comentário · Editado 03 de mar. de 2024 · Stephen Barbarino
0
Seguidores
0
Votos
0
Comentários
Stephen Barbarino comentou,
I'm glad it's not just me. We would love a search or toggle option to help reduce the field clutter when performing bulk edits.
Exibir comentário · Publicado 03 de jan. de 2024 · Stephen Barbarino
0
Seguidores
1
Votos
0
Comentários
Stephen Barbarino comentou,
Understood on the use case Ashwin, that does make sense. However this does limit the use of Zendesk as an internal ticketing platform. It seems that Zendesk is more focused on the B2C customer experience use case which is fine...I just think that those of us trying to use it as an ITSM tool will find it lacking in features and eventually need to make a move to a platform more suitable.
Exibir comentário · Publicado 09 de jan. de 2023 · Stephen Barbarino
0
Seguidores
0
Votos
0
Comentários
Stephen Barbarino comentou,
If we're using Azure AD SCIM provisioning and setting a users display name based on their preferred name while leaving their first name in azure set to their legal first name it shouldn't update the name in Zendesk during SSO.
Are there any plans to fix this? Telling us to "stop using SSO" isn't a sufficient answer.
Exibir comentário · Publicado 05 de dez. de 2022 · Stephen Barbarino
0
Seguidores
5
Votos
0
Comentários
Stephen Barbarino comentou,
Hi Ashwin, thanks for taking the time to address all of the questions individually, that's really appreciated. I'm not sure I fully understand the concern though. If a Zendesk customer doesn't want to expose data through lookup fields to their end customer through guide wouldn't they just not use a lookup field then?
Our use case around Zendesk is focused on an internal customer base where having the ability to lookup users would really help. When we were evaluating products to be used as an internal ticketing and service management platform, the Zendesk team said this would be possible but I can honestly see us outgrowing this solution in a few years without this functionality.
Exibir comentário · Publicado 17 de nov. de 2022 · Stephen Barbarino
0
Seguidores
0
Votos
0
Comentários
Stephen Barbarino comentou,
This is great, but I'd love for their to be a lookup field available for end users. For example, a manager submitting an equipment request ticket for an employee would select the employee in a lookup field.
It's a bit crazy this isn't already available.
Exibir comentário · Publicado 03 de nov. de 2022 · Stephen Barbarino
0
Seguidores
2
Votos
0
Comentários
Stephen Barbarino comentou,
Just wanted to add that we could really use this feature for our human resources employee onboarding processes. Due dates for specific requests are usually 5 days from the time of request.
Exibir comentário · Publicado 16 de ago. de 2022 · Stephen Barbarino
0
Seguidores
0
Votos
0
Comentários