Smartcard Website Authentication
Use your national Identity Card, eIDAS Token or Health Card to Authenticate
The Crucial Role of National ID, eIDAS Tokens, and Health Cards in Digital Authentication
Embracing national identity cards, eIDAS tokens, and health cards for website authentication marks a significant leap in online security. These methods offer superior protection against identity theft and cyber fraud compared to traditional passwords. Government-backed national identity cards and eIDAS tokens provide reliable, verifiable digital identities, while health cards ensure secure access to personal health data. Their integration is essential in fortifying digital transactions, promoting user trust, and adhering to regulatory standards in our increasingly digital world.
Accessible Through Your Smartphone
Contrary to popular belief, using NFC-enabled smartcards doesn't require a separate NFC card reader. Most modern smartphones come equipped with built-in NFC capabilities, making them ideal for reading these smartcards. This widespread accessibility dispels the myth that NFC technology is out of reach for the average user, opening up a world of secure and convenient authentication methods right at your fingertips.
Simplifying Integration with Open Protocols
The misconception that integrating national ID cards into systems is a complex and costly endeavor is being challenged by the advent of open protocols like OpenID Connect. These protocols facilitate a smoother and more affordable integration process, debunking the notion that adopting national ID card authentication is an arduous task. OpenID Connect, in particular, offers a streamlined approach, making this advanced authentication method more accessible to developers and system integrators.
CodeBs Public Nextcloud: A Prime Example of Seamless Integration
CodeBs Public Nextcloud stands as a perfect demonstration of how seamlessly national ID cards, eIDAS tokens, and health cards can be integrated into a system. This platform exemplifies the effective use of these authentication tools in a real-world application, showcasing the ease and efficiency of securing digital resources. CodeBs Public Nextcloud not only demonstrates the practicality of these methods but also serves as an inspiration for other systems looking to enhance their digital authentication processes.
Mobile devices now serve as platforms to access robust security anchors, making MSISDN and SIM cards redundant in the face of national identity card authentication
The Role of the CodeB Authenticator
The world is shifting rapidly towards more secure and user-friendly authentication methods. At the forefront of this change is the CodeB Authenticator, a mobile app that is transforming how we think about and interact with online security within the OpenID Connect (OIDC) framework.
The real power of the CodeB Authenticator lies in its ability to turn a mobile device into an Identity Provider (IdP). This functionality elevates the role of a smartphone from a mere tool for communication to a robust gatekeeper of digital identity.
What sets the CodeB Authenticator apart is its unique utilization of strong, smartcard-based identities via Near Field Communication (NFC) technology. This approach ensures that the authentication process is not only highly secure but also distributed and sovereign. By integrating smartcard technology, the CodeB Authenticator taps into a well-established realm of digital security, offering users a level of authentication strength previously unavailable in mobile-based solutions.
Scan QR Code to Login
When a user scans a QR Code using their mobile device, the QR Code graphically encodes a portion of the OIDC requests.
The CodeB Authenticator mobile app then securely interacts with the OIDC authentication server, triggering the authentication process.
The QR Code functions as a secondary transport mechanism, filling in gaps in mobile OIDC requests and significantly enhancing security by making data interception exceedingly difficult.
Boosting Security
Employing QR Codes as a secondary transport mechanism makes the authentication process more secure. Given that QR Codes are unique to each login attempt and have a limited validity period, intercepting and reusing them for unauthorized access becomes a daunting task for potential attackers.
This security advantage substantially mitigates the risk of man-in-the-middle attacks and other interception-based threats.
Experience it for yourself and log on to our Nextcloud using your national ID Card, Health Card or any other supported Token.
Install CodeB Authenticator
Download the CodeB Authenticator from the Google Playstore by scanning the QR Code on the right. After installing the CodeB Authenticator, please configure your mobile number and OIDC settings in the app.
PIN Activation
Many national identity cards or eIDAS tokens are issued with a default transport PIN or a null PIN. Prior to utilization, the user must alter these PINs to activate the card. For certain compatible tokens, the CodeB Authenticator can also serve as a tool for managing PINs.
Read more: CHANGING TRANSPORT PINS ON YOUR MALTESE IDENTITY CARD: A GUIDE
Use your ID Card to access our public Nextcloud
Accessing our public Nextcloud is straightforward. Simply select the "Log in to Nextcloud" button below, and a separate browser window will appear. Within this window, choose the "Log in with ID Card" option, as depicted in the accompanying image to the left.
This will prompt the CodeB Authentication dialog to appear. At this stage, ensure to select the "Use QR Code" option and scan the displayed code using the QR Scanner within your CodeB Authenticator app.
CodeB's inbuilt NFC Card Reader will now open its inbuilt NFC Reader asking you for your CAN Number.
CAN Number
The CAN, or Card Access Number, is a distinct identifier located on NFC (Near Field Communication) Identity Cards. Its primary function is to facilitate secure access to the card's data.
The CAN is composed of a 6-digit numerical sequence. This number is typically printed on the front side of the NFC Identity Card for easy reference.
Post CAN Number entry, the user is required to confirm the input by pressing 'OK' or a similar confirmation button on the device.
Following confirmation, the user should position their mobile device directly over the NFC Identity Card. Proper alignment is crucial for successful communication between the card and the device.
Once the haptic feedback is confirmed, the user should observe the progress bar displayed on their mobile device's screen. This bar will typically feature a series of dots or a similar visual indicator.
The user is required to wait until all the dots in the progress bar turn green. This change in color signifies that the authentication process is proceeding correctly and is nearing completion.
It is crucial during this stage to maintain the position of the NFC Identity Card under the mobile device. Removing or repositioning the card prematurely may interrupt the authentication process, necessitating a restart of the procedure.
Authentication PIN
Each card is typically equipped with two distinct Personal Identification Numbers (PINs) designed for different purposes.
The "Signature PIN" is exclusively used for creating Qualified Electronic Signatures (QES), a critical component in digital document signing.
The "Authentication PIN," on the other hand, is utilized for the operation of authentication and decryption certificates. It is this PIN that is required when authenticating to a website.
To authenticate on a website, the Authentication Certificate associated with your card is employed. Consequently, you will need to enter your Authentication PIN.
Prior to this step, ensure that your card is not in its initial transport state. This necessitates changing the default transport PINs or NULL PINs to personalized ones.
Proceed to input your Authentication PIN into the designated field on the authentication interface.
After entering the PIN, confirm the action by selecting 'OK' or an equivalent confirmation command.
Similar to previous steps involving NFC, it is essential to keep the card steady and in close proximity to the mobile device's NFC field. Avoid any movement or repositioning of the card while the NFC field is active and the authentication process is underway. Movement can disrupt the process and may require a restart of the authentication sequence.
Your Nextcloud user account is now being created, and you are simultaneously being logged in.
Looking for Microsoft Azure AD B2C Integration? Dont miss:
Integration of CodeB Authenticator with National Identity Cards and Hardware Tokens