Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-39253: Can an existing OATH OTP that is set up on one tenant be used as an MFA option for a second federated tenant?

Authentication Service ,   Privileged Access Service ,  

21 August,20 at 02:47 PM

Question:
Can an existing OATH OTP that is set up on one tenant be used as an MFA option for a second federated tenant?

Answer:
Unfortunately, the existing OATH OTP from one tenant cannot be used on another federated tenant.

OATH tokens are attached to the host name when created, its part of the protocol (and embedded in the 'data' used to generate OTPs). So if the OATH token was created for .my.centrify.com, it can't work on .my.centrify.net.

For interactive login (not agents, ssh/rdp) for a federated user, redirection to the IDP occurs, and OATH token is usable (as authentication is occurring on the IDP at its host name). For cases like SSH/RDP/agents, there is not redirection, so the OATH token registered to the IDP cannot be used.

Related Articles

 articleCentrify 17.6 and 17.6 Hotfix Release Notes article[Labs] Using YubiKey (PIV or OATH OTP) to Secure Centrify Identity Service and Privilege Service article[LABS] Setting-up the MFA for Servers feature of Centrify Server Suite 2016 articleKB-20836: Tenant Migration FAQ for joint customers of Centrify and Idaptive articleCentrify 17.7 Release Notes articleCentrify 19.5 Release Notes articleCentrify 18.2 Release Notes articleCentrify® Cloud 16.4 Release Notes articleCentrify 17.2 and 17.2 Hotfix 1 Release Notes