Google’s new Android O features will improve SMS Authentication Services. Most applications (as mainly used for messaging) ask you to validate your contact number by entering a confirmation code. You can either enter this time-sensitive code by hand or grant the app the authorization to read your incoming SMSs so it can find and enter the code for you. This is done to confirm a user and their device’s identity being used.
These One Time Passwords (OTPs) are a necessity in our present hi-tech culture. They assist in guarding customers against fraud and shield their bills and personal records via SMS authentication. SMS companies also have integration with key phone networks to certify that SMSs are delivered instantaneously, to just about any country worldwide, which makes it a convenient and fast method to obtain verifications.
At the recent Google I/O 2017 conference it was announced that their new operating system, dubbed Android O, will introduce a dedicated API that applications can employ to scan and acquire verification codes sent via SMS, so these apps will no longer need to get authorization to check incoming messages.
What is OTP SMS Verification and how does it work?
OTPs are special codes used when a client signs on to or tries to get to access individual data. A One Time Password (OTP) is an automatically produced numeric or alphanumeric series of characters that verifies the client for a solitary exchange or session, which means they will terminate after a specific amount of time.
Individual OTPs are sent to a user by means of SMS, email, or through a computerized telephone call, however SMS is the most well-known method. This is the most significant approach to verify the client since these days 90% of individuals are using telephones so they think that it is more convenient to open SMS on their cell mobile device screen as opposed to opening an e-mail or getting a voice call.
OTP SMS confirmation or verification is mainly for retrieving, resetting and changing passwords, new user registrations, downloading apps and granting them certain permissions. Mobile phone based validation with SMS and real-time number checks give the perfect blend of ease, security and safety, and affordability. These limitations are set up to protect the user.
The new method as revealed by Google to be integrated as API inside their new OS will eradicate the need for clients to physically enter OTPs. Applications will have the capacity to ask for an 11-digit code for OTP SMS validation and will alert the Android operating system to look out for the code.
At the point when an SMS verification message is received, the OS will read the message and send the OTP code to the application. Android will start noting any incoming SMS for a specific OTP token. At the point when the SMS containing the token is received, this process sends the token straight to the application without it having to read an SMS. The OTP message is never actually sent to the inbox after the message has been received for validation, the SMS with the token is directed as usual.
As consumers are becoming more and more demanding about their online security and privacy, this new feature and API was added to regulate and protect data transfers to cloud storage and emails, online banking and trading applications. It will also ensure a more fluid validation process that doesn’t require the user to actively go through as many steps for verification.
The method of sending OTPs via SMS as two-factor verification is still widely used throughout the world by online trading and banking services among others. With more than six billion mobile phone numbers registered worldwide, the mobile phone number is becoming the ultimate way to verify user identity as it best links both a user and device to an account.
The main benefits of this featured change with regards to receiving OTPs via SMS is that these messages will no longer arrive in the chosen SMS inbox and apps will no longer require permission to read every incoming text message or to have access to your complete message history. Developers will also find this useful as it means there is one less permission requested by an app when you set it up.
This new method will eliminate the need for users to wait for an SMS authentication message to appear and users also won’t be required to switch between the SMS app and the program needing a code. The SMS also won’t show up in the user’s inbox, meaning less clutter.
This update to the OS integration features which will be included in Android O is still in the developer preview phase, but according to Google, it will most likely be released to public users towards the end of August or September 2017. At the time of writing, there have not been any similar feature updates on the iOS for Apple devices, but rather only third party applications and developer patches to cover automatic OTP verification.