When a team (with members potentially located in different places) works on a development project, it is essential to have
identification and
authorization mechanisms in place. These mechanisms are key in the case of GeneXus Server, as in every installation you can catalog different knowledge bases (KB), and you can perform different operations on each KB. On the one hand, it is important for those who are involved in a project (KB) to be identified (authenticated) so that it is possible to know who does what. On the other hand, authorization is also critical to determine who is authorized to do what. In order for everyone involved to work in an environment of trust, and sometimes for auditing purposes, it is important for each person to work freely and carry out only the tasks they are authorized to perform.
GeneXus X Evolution 1’s Release Candidate allows for local authentication (Users defined in GXserver) and/or GXtechnical authentication, which means that you can access the Server using the account you have defined in GXtechnical (this is the authentication used by the
GXserver which is available at no cost to the Community).
The Release also includes the capability to grant permissions.
See the How to in the
CommunityWiki.