2.9 Implement role-based security in F&O apps

Question 1

How does security work in F&O?

Answer 1

Access is not granted to individual users, but to security roles to which the users are assigned
A user who has a role, has access to a set of privileges that are associated with that role

Question 2

What can roles contain?

Answer 2

Privileges
Permissions
Duties

Question 3

Permissions?

Answer 3

Access to individual securable objects, such as menu items and tables

Question 4

Privileges?

Answer 4

Composed of permissions, represent tasks, such as generating a sales order
Privileges give the user access to perform a specific action

Question 5

Duties?

Answer 5

Composed of privileges and represent parts of a business process, such as maintaining vendor information

Question 6

Permission policies?

Answer 6

Are used in role-based security to grant access to users for specific purposes

Question 7

What is used to assign data security policies to security rikes?

Answer 7

Extensible Data Security (XDS) framework

Question 8

Extensible Data Security definition?

Answer 8

Evolution of record-level security (RLS) that was available in AX 2012.
Allows you and the admins of your org to help secure data in shared tables in such a way that users will have access to the part of the table that is allowed by the enforced policy

Question 9

Flow of XDS?

Answer 9

1. Start with query to define the ranges that should be placed on tables
2. Create security policy that links to the query and primary table for which you want to restrict data access
3. Define the context for the rule.
4. Define the list of constrained tables, which are related tables that store data from the primary tables

Question 10

Where are users assigned to security roles in front-end?

Answer 10

Security administration -> Security -> Security configuration