Bobcares

How to resolve OnApp YubiKey authentication failure

by | Sep 13, 2021

Wondering how to resolve the onapp YubiKey authentication failure issue? We can help you with this!

As part of our Server Virtualization Technologies and Services, we assist our customers with several OnApp queries.

Today, let us see how our support techs help our customers to fix the onapp YubiKey authentication failure issue.

 

OnApp YubiKey authentication failure

 
We will receive the following error when we try to log in to the OnApp under the admin account protected with Yubikey:

Service is temporarily unavailable and Invalid Yubikey

This authentication failure is due to expired certificate inside ‘Yubikey’ gem. We need to update the certificate chain to resolve the issue.
 

For OnApp version 5.0 to 5.4

 

  1. Firstly, we need to download the chain.pem file to CP from YubiKey Authentication page.

2. Then we should change the owner of the patched .pem file.

# chown root:root #pem_file_location#

3. After that we need to locate and take a backup of the current chain.pem file.

# find /usr/lib*/ruby -name \*chain.pem
/usr/lib64/ruby/gems/2.1.0/gems/yubikey-1.4.1/lib/cert/chain.pem
# cp -av /usr/lib64/ruby/gems/2.1.0/gems/yubikey-1.4.1/lib/cert/chain.pem /usr/lib64/ruby/gems/2.1.0/gems/yubikey-1.4.1/lib/cert/chain.pem.bak

4. Now put into place new chain.pem file.

# cp -av #pem_file_location# /usr/lib64/ruby/gems/2.1.0/gems/yubikey-1.4.1/lib/cert/chain.pem

5. Finally restart the OnApp Control Panel services like onapp, httpd.
 

For OnApp 5.5  to  6.0

 
1. At first, run the following command:

# yum update rubygem-yubikey

2. Then restart OnApp Control Panel services like onapp, httpd.
 

For OnApp versions 6.1

 
1. Firstly, run the following command:

# yum update rubygem-onapp-core

2. Then we should restart OnApp Control Panel services like onapp, httpd.
 

For OnApp versions 6.2

 
1. Firstly, we need to download the chain.pem file to CP from YubiKey Authentication page.
2. Then we should change the owner of the patched .pem file

# chown root:root #pem_file_location#

3. After that we need to locate and backup the current chain.pem file

# find /usr/lib*/ruby -name \*chain.pem
/usr/lib64/ruby/gems/2.5.0/gems/yubikey-1.4.1/lib/cert/chain.pem
/usr/lib64/ruby/gems/2.5.0/gems/onapp-core-6.2.3/config/yubikey_cert_chain.pem
# cp -av /usr/lib64/ruby/gems/2.5.0/gems/onapp-core-6.2.3/config/yubikey_cert_chain.pem /usr/lib64/ruby/gems/2.5.0/gems/onapp-core-6.2.3/config/yubikey_cert_chain.pem.bak

4. Now put into place new chain.pem file

# cp -av #pem_file_location# /usr/lib64/ruby/gems/2.5.0/gems/onapp-core-6.2.3/config/yubikey_cert_chain.pem

5. Finally restart OnApp Control Panel services like onapp, httpd.

[Need more assistance with OnApp queries? We’d be happy to assist]
 

Conclusion

 
In short, today we saw how our Support Techs help our customers to fix the YubiKey authentication failure issue.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF