" /> Genesys Emails Works With Digital ID encryption ? - Genesys CTI User Forum

Author Topic: Genesys Emails Works With Digital ID encryption ?  (Read 1863 times)

Offline raza990

  • Full Member
  • ***
  • Posts: 214
  • Karma: 5
Genesys Emails Works With Digital ID encryption ?
« on: November 18, 2015, 09:54:23 AM »
Advertisement
Hi Guys,

We are trying to setup an emails with Digital ID encryption where agent should enter password to open email on desktop which came to some XYZ authorities with some Digital ID certificates in it.

Outlook client can have this functionality and customer want us to setup this in our desktop.

We are using agent desktop - but as I read documentation, Genesys havn't discussed about this type of encryption method in it documentation so I' assuming that we have nothing to do this in Genesys configuration. However, we can only do this by customization of agent desktop where it detects emails which have Digital ID related thing in it and will popup a windows for asking a password to agent.

I would like if you guys provide your opinion on this and suggest some good ways so I can move further with this task.

Thank you

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Genesys Emails Works With Digital ID encryption ?
« Reply #1 on: November 18, 2015, 01:48:23 PM »
Do you mean the Digital signed emails? If yes, I think that it is not currently supported by the ESJ (without any customization), so will have to open a #FR on Genesys.

Offline raza990

  • Full Member
  • ***
  • Posts: 214
  • Karma: 5
Re: Genesys Emails Works With Digital ID encryption ?
« Reply #2 on: November 18, 2015, 06:16:33 PM »
Yes Kubig, I meant Digital signed emails - I think now we only can do this by agent desktop customization.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Genesys Emails Works With Digital ID encryption ?
« Reply #3 on: November 19, 2015, 01:18:57 PM »
I do not think so, because as I remember, the ESJ does not proceed emails such like that (maybe it is solved in any newer version)