Public URL's sent to customer are too long for public tickets
started a topic
almost 5 years ago
I was initially worried that public tickets would have the ticket id attached and some spammer could sequence thru all public tickets to steal emails and other sensitive information.
I was glad to see that public emails had a hash key attached to stop anybody from trying this.
However this hexadecimal hash key is 64 characters long and creates long url's and look rather spam like, not to mention that it may break into multiple lines in some browsers.
I realize that there is a need for security but a 64 bit key will produce over 1x10^77 combinations, which is extreme overkill. How can I have the hash key restricted to something more reasonable, like 16 digits. This will still provide extremely good security without looking spamlike or having the URL broken across lines.
To me, this seems like something that should be configurable. There's clearly a balance to be struck between security and URL length, and as Freshdesk customers, I think we're best positioned to decide how long the hash should be for our Freshdesk instance.