Configuring user profiles

Working sessions in siguanet-desktop are tied to user profiles. The concept is introduced in the Generating remote settings files and the Application configuration pages. These are the points you should already be familiar with:

• You should create one .srs file per profile, so that standard users don't have to manually connect to PostgreSQL.
• You should deploy the corresponding .srs file through HTTP so that, upon application login, siguanet-desktop can build the PostgreSQL connection string according to the user's profile.
• You should create one .sgd file per profile in order to define the set of functions which meets the needs of each user's profile.
• You should deploy the corresponding .sgd file through HTTP so that, upon application login, siguanet-desktop can enable and load those tools that are suitable for the user's profile.

Here we'll focus on profile management and how to create and deploy profile definition documents, also named siguanet-desktop documents ( .sgd ).

Profile management

There are 5 predefined user profiles embedded in siguanet-desktop's object model, as seen in the ProfileType enumerated type:

• Publico is intended for users who choose anonymous access on application login, that is, people who don't strictly belong to your organization and are not provided with means of identification.
• Interno is intended for users within your organization.
• Departamento is intended for users who have intermediate management responsibilities within your organization.
• Administrador is intended for users that have governing or executive responsibilities within your organization (e.g. university chancellors or vice-chancellors).
• Root is a special profile reserved for application and system administrators.

You should create an .sgd file for each of the 5 base profiles, typically in a cumulative way. The default profile discovery method uses the personal table in your SIGUANET database as a backend, although you can provide your own discovery logic, as explained in the Implementing user authentication page.
As for the built-in discovery method, users who access siguanet-desktop anonymously or cannot be authenticated are assigned the Publico profile. On the other hand, authenticated users are assigned the Interno profile.