/o//commerce-media/accounts/-1/images/18528194?download=true
YubiKey OTP Login
DXP App
With this hook you can integrate a new Liferay's authentication in your portal.
Through the Portal Settings you can choose email + OTP or email + password + OTP authentication way.
The OTP must be registered on the site of a YubiKey Yubico fact for validation in the background are called API Yubico.com.
Each user can authenticate / register using YubiKey one at a time, in fact the DeviceId or also called PublicId is associated with the user at the time of provisioning itself. If necessary, the user can authenticate with another YubiKey but the DeviceId must be "new", that is not being used by another user on the same portal.
Small note: If the portal administrator HAD DISABLED FURTHER CONTROL BY PASSWORD, so users can only authenticate with email + OTP, then DeviceId must be the same as last access facts, it does not run an overwriting of DeviceId (operation only possible with user + pwd + OTP)
Through the Portal Settings you can choose email + OTP or email + password + OTP authentication way.
The OTP must be registered on the site of a YubiKey Yubico fact for validation in the background are called API Yubico.com.
Each user can authenticate / register using YubiKey one at a time, in fact the DeviceId or also called PublicId is associated with the user at the time of provisioning itself. If necessary, the user can authenticate with another YubiKey but the DeviceId must be "new", that is not being used by another user on the same portal.
Small note: If the portal administrator HAD DISABLED FURTHER CONTROL BY PASSWORD, so users can only authenticate with email + OTP, then DeviceId must be the same as last access facts, it does not run an overwriting of DeviceId (operation only possible with user + pwd + OTP)
DEVELOPER
Francesco Pasturenzi
DEVELOPER
08.10.15 00:00
Published date
Fehler bei der Verarbeitung der Vorlage.
The string doesn't match the expected date/time/date-time format. The string to parse was: "08.10.15 00:00". The expected format was: "MM/dd/yy HH:mm".
The nested reason given follows:
Unparseable date: "08.10.15 00:00"
----
FTL stack trace ("~" means nesting-related):
- Failed at: ${CPDefinition_displayDate.getData()?... [in template "3192443#3192485#null" at line 4, column 9]
----
1<#setting date_format="MMMMM d, yyyy">
2
3<#if (CPDefinition_displayDate.getData())??>
4 ${CPDefinition_displayDate.getData()?datetime("MM/dd/yy HH:mm")?date}
5</#if>
Published Date
08.10.15 00:00
SUPPORTED OFFERINGS
Self-Hosted, Self-Managed
Supported Versions
6.1
Resource Requirements
Edition
CE, EE
PRICE
Free
help & support
Terms & Conditions
SHARE LINK
HTML Example
A paragraph is a self-contained unit of a discourse in writing dealing with a particular point or idea. Paragraphs are usually an expected part of formal writing, used to organize longer prose.