ReCRED had a strong presence in MWC2018. Fruitful discussions took place with FIDO alliance, Service Providers, developers and investors.
More details can be found here.
ReCRED had a strong presence in MWC2018. Fruitful discussions took place with FIDO alliance, Service Providers, developers and investors.
More details can be found here.
This video demonstrates a two-factor authentication scenario where the user tries to authenticate to a Service Provider (SP) from his desktop browser. Initially, the SP redirects the user to an OpenID Connect Provider to authenticate using FIDO UAF and by scanning a QR code using his ReCRED mobile application. Upon successful FIDO authentication, the SP requires additional verification using a Behavioral Attribute Authority (BAA). In this case, the SP requests from the Identity Consolidator (IDC) a list with the BAAs that are associated with the user. As soon as the user chooses the BAA that he wants to use for second-factor authentication, the SP contacts the BAA and requests behavioral authentication for the user. At the end, and when the BAA has verified that the user currently behaves as he always does, then the user gets access to the SP. This video has been created to demonstrate WP3 – Device Centric Authentication tasks.
This video demonstrates how continuous authentication works and especially the case when a Behavioral Attribute Authority (BAA) detects that a user is not behaving as usual on his mobile device. In this case, the BAA contacts the Identity Consolidator(IDC) through the 3rd Party API in order to trigger Latch and lock the accounts of the user. Then the 3rd Party API notifies Latch and if the user has enabled Latch then all the accounts of the user get locked. This video has been created to demonstrate WP3 – Device Centric Authentication tasks.
This video demonstrates how the user can regain full access to his Identity Consolidator (IDC) account using the failover authentication options that ReCRED provides in case of device loss/theft or failure. The user authenticates with the IDC using his master password and upon successful authentication he gets access to the IDC only in tentative mode. Under tentative mode the user has limited access to the IDC functionalities. In order to regain full access he has to perform failover authentication either with a Behavioral Attribute Authority (BAA) or with a MobileConnect (MC) provider. This video clearly demonstrates both BAA and MC failover authentication. This video has been created to demonstrate WP3 – Device Centric Authentication tasks.
This video demonstrates the process of declaring and verifying the address of a user using a utility bill. By the use of the ReCRED Android App, the authentication to the Identity Consolidator (IDC) using FIDO and OpenID Connect is demonstrated. Subsequently a demonstration of the verification of an NFC enabled passport using the NFC functionality of the Physical Identity Acquisition module is shown. This video has been created to demonstrate WP4 – Identity Consolidation tasks.
Co-funded by the Horizon H2020 Framework
Programme of the European Union under grant agreement no 653417
The content of this website reflects only the views of the project owner. The European Agency / Commision is not responsible for any use that may be made of the information it contains.
