Why can’t the screen display messages sent by OPPO R9s?

It is not displayed because the notification is not turned on.

Configure settings in the message notification bar. Go to Settings - Security and Privacy - Notification Center on your phone and select the software to turn off and turn on notifications. In addition, you can also turn it on in Settings-Notifications and Status Bar-Notification Management. ?

How to set software permissions:

1. In ColorOS 3.0 system, enter the mobile phone manager--Permissions Privacy--App Permissions Management--Modify the applications that need to modify permissions;

2. ColorOS version 2.1, Security Center – Permission Privacy – Application Permission Management;

3. ColorOS 2.0 version, Security Center – Permission Management – ??Application Permission Management;

4. For other versions, set--security service--personal information security. Permission management?

Permission management generally refers to the fact that according to the security rules or security policies set by the system, users can access and can only access the resources they are authorized to do, no more, no less. Permission management appears in almost any system, as long as there is a system with users and passwords. Many people often confuse concepts such as "user identity authentication", "password encryption", and "system management" with the concept of rights management.

What does the permission system do?

Give a set of methods to identify, organize, and host all functions in the system, and organize and identify and host all data. , and then provide a simple and unique interface. One end of this interface is the application system and the other end is the permission engine. What the permission engine answers is only: Who has the permission to perform a certain action (movement, calculation) on a certain resource. The only results returned are: Yes, No, and the permission engine is abnormal.

Basic concepts

User identity authentication does not belong to the scope of rights management at all. User identity authentication is to solve this problem: the user tells the system "who am I", and the system asks the user how to prove that you are "who"? For systems that use username and password authentication, then the password is required. When the username and password match, it proves who the current user is; for systems that use fingerprints and other systems, the fingerprint is required; for card swiping systems such as hardware Key, the card needs to be swiped.

Password encryption belongs to the field of user identity authentication and does not belong to the scope of authority management.

Pay attention to the problem

A poor permission management system will inevitably leave system loopholes for hackers to take advantage of. Many software can easily obtain unauthorized data through URL intrusion, SQL injection and other modes. System data may even be modified or deleted, causing huge losses.

Many systems, especially those using hard coding, have permission logic that is tightly coupled with business code and scattered throughout the system. There are bound to be many system vulnerabilities, and as the system continues to be modified, the number of vulnerabilities will gradually increase. A good system should centralize permission logic and have it set and parsed by a professional security engine. The business logic calls the security engine to obtain the permission results, and the non-professional mode is no longer used. This transformation is as shown in the figure: authority is transformed from tightly dispersed to centralized professional management

System management is generally a module of the system. Moreover, this module generally also contains a rights management sub-module. Therefore, many people mistakenly believe that the permission management system is just a small sub-module of the system. The rights management module in system management is just an operation interface that allows enterprise IT administrators to set security policies such as roles. There is a lot of permission verification logic behind the system, which does not belong to this module. Generally speaking, this module is equivalent to providing some data to the authority management module, for example: Zhang San is the human resources manager, etc.