EDAMS System Administration
Frequently Asked Questions
July 2010

• How do I check using a query which users belong to certain security profiles?


• How can I create security groups and profiles?


• How can I set up user definable password policies?

---

   

How do I check using a query which users belong to certain security profiles? 

To check which users belong to a certain security profile use the following script :

select d.ORGPOST_NO,  d.DESCRIPTION, a.PROF_SID, a.PROF_NAME, b.GRP_SID,

       b.GRP_NAME, [User_Name], Initial, surname,

       f.*

 from SEC_PROFILES a, SEC_GROUPS b, SEC_GROUPS_PROFILE c, ORGPOSTS d, EMPLOYEES e,

      SEC_ACES_SID f 

where a.PROF_SID = c.PROF_SID

  and b.GRP_SID = c.GRP_SID

  and d.PROF_SID = a.PROF_SID

  and e.ORGPOST_NO = d.ORGPOST_NO

  and c.GRP_SID = f.[SID]

order by b.GRP_SID

Back to Top

---

      

How can I create security groups and profiles?

To create security groups and profiles do the following :

i. Check if an existing Security Profile is already assigned for these users.

Identify a user in Customer Services for whom you want this security setup

System Administration à Organization à Human Resources à Personnel Administratio

Check the Post these users belong too (see above), I would assume it is CUST : Customer Care

Check to which Security Profile this Post is assigned, in the case of CUST it seems to be customer case privilleges (see below)

System Administration à Organization à Structure à Posts

Check if Security profile setup already assigned to this Profile

Go to System Administration à Organization à Structure à Security Profiles

This security profile has the Group No Changing in customer details assigned to it already

You can either assign more security settings to this group or create a new group.

ii. To create a new security Group to this profile as to add extra security changes.

Add a new group on right panel, which will be used to assign additional restrictions

E.g add a group called CS - Limit Change of Information

1. Select Group Panel

2. Select +

3. Give Name

Now select the customer care priveliges profile on left pane and select CS - Limit Change of Information on right pane and select  << to assign the group to Profile on left

It should now be added (see below)

Now we have 2 groups belonging to this Profile.

 

iii. Setting Up the Security Limitations to this Group.

Login to EDAMS using a user that has the SysAdmin Utility Typical Post, EDAMS users is such a user (see below)

Select screen where you want to apply Security Profile

 e.g.  Customer Services à Notification of Change of Customer Details

We do not want to be able to change the Telephone No for example.

Press Alt + F3 + Ctrl.  (in this order)

Right click on control for which you want  to apply security to, in this case Telephone No.

Select the group to assign security too, this must be one of the groups we identified or create above.

Select that we only want the user to Read. If we do not select any then it means the control will be made invisible, then select ok (see below).

NOTE. It is better to hide buttons (select no option) than to disable them (by choosing Read), as many times in program we disable or enable buttons programmatically, which will bypass the security setting.

To save changes once done you need to exit the form on which control is located, and you are done.

Observation

Please also note that for example the Surname is already assigned to a previous profile by you called No Changing in customer details. Too see this select Surname and right click

You will see that the group that No Changing in customer details is already assigned security

If we check the Telephone No. We should find our setup, which is read only

TO CHECK

If I now login as a customer care user eg. MALLS, you will find the control is disabled (see below).

 

Back to Top

---

      

How can I set up user definable password policies?

Password policies that are user definable have been added under Sys Admin --> Project --> Parameters --> Passwords.
If you do not set any of these policies (see screenshot) you should be able to work as you did before. 

At time of login these policies are checked and if the user's current password does not meet the policy conditions, the user is forced to change the password to meet policy.

NB!! Be sure to note that passwords are now case sensitive, (the default which is the same as user name when a password is reset, remains the same with all letters uppercase).

In addition there is a new option to disable a certain user from logging in to EDAMS (e.g. If that user has left the organization)

These changes require upgrade to your DB using db scripts, otherwise you will not be able to access EDAMS.

 

Back to Top