A Quick Review
Android 12 — Lock Screen Notification Security
In this post, I continue to explain the new features that will be part of our lives with Android 12. Those who are wondering about the first article on App Overlay Controls can read through this link.
Notifications are device features that can contain personal information. Therefore, their security is also of particular importance. When the screen is locked, people may not want others to either access the notification contents or interact with the notification buttons. For content accessibility, the operating system already demands authentication if it is configured to do this, however, security could not be configured so flexibly for buttons until now.
Android 12 has come up with a security improvement in this regard. An authentication request can now be added to any notification button (action).
So How Will This Happen?
Android 12 has introduced a new flag setAuthenticationRequired. This flag will be applied to actions while constructing notifications. In other words, even if the action does not open an activity or direct reply, authentication can be requested from the operating system. Example usage is as follows:
With this improvement, even the “mark as read” button will now be able to request the lock screen to be opened 🎉
See you in the next post.
