20 Reasons to Migrate Magic eDeveloper, uniPaaS and Magic xpa to
.NET by Upgrading Rather than Converting
Magic greatly simplifies security issues for developers, giving
them the power to create highly secure applications without a lot of hassle.
This is another reason why Magic eDeveloper
or uniPaaS to .NET migration via C#.NET is a mistake compared to upgrading
to .NET with Magic xpa.
User rights management is simplified in Magic because the
developer and administrator/supervisor use Magic xpa’s built-in Authorization
System, Active Directory or LDAP. The Authorization System enables developers
and certain users to control access to Magic xpa projects in Studio modes. This
control is achieved through setting access keys to various Magic xpa project
elements, and by assigning specific rights to users and user groups.
As a repository based system, Magic xpa is vastly superior to the
tedious coding required for rights management in C#. The Magic xpa Rights
repository lists the name and keys of all the rights defined for a project. The
developer can define a bank of rights and assign them to the project's various
repositories and elements. Any project element that has an access right
assigned to it will be blocked to users who have not been assigned this right.
Project-layer security is always defined during development.
In addition, Magic xpa includes a flexible authorization system to
control what each user can and cannot do in Magic xpa. The authorization system
lets the application developer or system supervisor limit access to various
activities in Magic xpa to those users specifically authorized to have such
access.
The
authorization system exercises its control through sets of rights and the use
of built-in Magic xpa functions. Rights can be thought of as keys to locks.
Rights assignments connect users, who are classified by role, with the
application’s components, which are classified by accessibility. This means
that certain classes of users are allowed to access certain parts of an
application.
The
person in the role of Supervisor can assign rights that give each user access
only to the activities for which that user is authorized. Any activity that is
not specifically restricted by the Supervisor or the developer remains
accessible to all users and does not require any rights assignment. To access
the authorization system repositories, the developer must log on to the system
as a user which has the SUPERVISOR GROUP assigned to the user. This group is
reserved by Magic xpa, and is automatically included in any Magic xpa system.
In addition, a Supervisor user (which has this group assigned to it) is also
automatically included in any Magic xpa system.
Typically, when one is implementing a security
system in Magic xpa, rights are granted according to the user’s job function,
which corresponds to a Magic xpa Group. That is, a user who is a bookkeeper will have a
different set of menus and screens than a person who is in Sales. Other rights,
however, may only be granted to certain individuals, such as the ability to
approve paychecks or adjust time cards.
Managing rights in C# can be like looking for a
needle in a haystack. Instead of having to search through potentially millions
of lines of code to find everywhere that a role is checked, Magic xpa provides
a single, consolidated location known as the Rights Repository. What a
nightmare it would be to have to parse an entire code base to learn and
document what roles are assigned to what permissions.
For additional information on how an upgrade to Magic xpa is
superior to Magic eDeveloper to
.NET conversion please convert
here.
No comments:
Post a Comment