Memority provides authentication via Secure Cookie (“Trust this device”), which is mostly used in B2C contexts.
Enrollment
Enrollement is self-service. It is performed by the end-user with a “Trust this device” button. Trusting a device will create a cookie on the corresponding browser, allowing for transparent authentication. The generated cookie is signed and encrypted, and cannot be forged.
Administration
Trusted devices can be managed from the user interface. Users can remove or rename their enrolled devices.
Authentication Process
Authentication is transparent on trusted devices.
Read Next
-
FIDO2 For Windows Hello, Yubikeys & Passwordless Authentication My-Access offers Passwordless Authentication using Fido2 or Windows Hello tokens. FIDO2 is the passwordless evolution of FIDO U2F.
-
OTP SMS / Mail authentication My-Access offers authentication via OTP sent by email or SMS, compatible with authentication to access Web applications, mobile applications and heavy clients.
-
OATH For Authenticator Apps My-Access offers authentication through OATH to generate TOTPs on mobile Authenticator Apps such as Google Authenticator, Microsoft Authenticator or any other eligible application.
-
x509 Certificates For Chip Cards & Badges My-Access offers Authentication using x509 certificates, namely for chip card (badges) authentication or for certificates stored in browsers.
-
Passwords (Including LDAP/AD passwords) Memority offers password authentication natively.
-
IDP Proxy My-Access supports SAML2, OIDC and OAuth2 protocols as Service Provider (SP) in a scenario where user authentication/authorization is delegated to an external Social Network (Meta, Google, X, etc.) or private third party Identity Provider (IdP) using their own local credentials.
-
Kerberos Authentication My-Access supports transparent Kerberos authentication.
-
Secure Cookie