Skip to main content

TableĀ 3 Various types of authentication in the SAMS

From: Secure Authentication-Management human-centric Scheme for trusting personal resource information on mobile cloud computing with blockchain

Authentication type Description
Client node does not create a block with its own information The client node cannot connect to the blockchain because it attempts to receive authentication by sending its own information and block to all the connected mobile devices
Client node attempts to change an already connected block Even if one client node changes all of its blockchain, it takes a long time to change the blockchain stored in the other mobile devices
Client node falsifies its own data and spreads it The connection is impossible because the authentication conditions (at least three of all mobile devices connected in the SAMS and at least 51% of all mobile devices) have not been met