In earlier versions, authorization was performed primarily on the client. This
meant there could be discrepancies between how permissions were validated by
the Windows client, by the Enterprise Portal client, and by other client types.
The addition of the Table Permissions Framework (TPF) to some tables in
Microsoft Dynamics AX 4.0 and Microsoft Dynamics AX 2009 shifted some
authorization to the server. TPF was limited to denying users access to full
records, but could not restrict individual fields from being visible. In Microsoft
Dynamics AX 2012 TPF is extended so that it can also work on fields. This shifts
more of the security load to the server. This helps to increase the consistency of
security between client types.
Regards,
Hossein Karimi
Monday, July 23, 2018
Server Enforcement of Security
Labels:
AX 2012,
Installation,
Security
+10 years of experience with hands-on lead-level background in the full life cycle of software development with demonstrated cross-functional team leadership skills.
Programming:
• ERP :Microsoft Dynamics AX 2012
• Language :X++, C#, C++, XAML, Asp.Net, Html, VB.Net, Android
• Environment : Windows XP, Windows 8, Windows 10, Windows Server
• DataBase : Oracle 9i,10g,11g and SqlServer and SQLlite
Subscribe to:
Post Comments (Atom)
Configure the Firewall on the Enterprise Portal Server
After you install Enterprise Portal, enable Web Server (HTTP) in Windows Firewall. If you do not enable the web server in Windows Firewall...
-
In Reporting Services, reports and resources are processed under the security identity of the user who is running the report. If the report ...
-
The below select query will give the both the Sales Line record count and the sum of sales quantity. static void Test_Data(Args _args) ...
-
To integrate Microsoft Dynamics AX and Analysis Services, you must connect Analysis Services to the Application Object Server (AOS). To do s...
No comments:
Post a Comment