Skip to main content
Closed for Voting

Assign an user role to the SSO shared secret

Related products:Freshdesk
  • September 23, 2015
  • 3 replies
  • 57 views

Once you have the SSO shared secret you can login with any type of users (Customers, agents, or God too). This means that you must 100% trust the external website.


Would be a nice security feature to be able to create (and revoke) SSO shared secrets and associate any shared secret to an user role, for example:


SSO key: XYZ123

Role: Agent


Means that using the key XYZ123 only users with "Agent" role will be accepted via SSO.


SSO key: ABC5678

Role: User


Means that using the key ABC5678 only users with "User" role will be accepted via SSO.

3 replies

  • Community Debut
  • September 23, 2015

We are planning to alter the SSO feature such that when an SSO request is received, we will check whether the SSO feature is enabled or disabled in Freshdesk. If SSO is disabled, we will not allow SSO access to Freshdesk even if the token is picked from Freshdesk SSO portal.


Invalidating the SSO token in case a Freshdesk account owner thinks a token has been compromised and generating a new one is also under evaluation.


However, removing the users that should not have access to Freshdesk is something we would still trust the SSO implementation to control.



  • Community Debut
  • August 13, 2017

Hello! Is generating new SSO token already implemented ? I can not find this option anywhere.


aravind.sundararajan
Skilled Expert
Forum|alt.badge.img+12

Hello,


We've pushed out a fix on production to handle this case. Now, when the SSO request is received, we'll check whether the SSO feature is enabled or disabled in Freshdesk.


Cheers!