Administration of staff and users
From MedITEX - Wiki
(3 intermediate revisions by one user not shown) | |||
Line 88: | Line 88: | ||
</tbody> | </tbody> | ||
</table> | </table> | ||
+ | <h2>Import/synchronization of users from Active directory</h2> | ||
+ | <p><span id="docs-internal-guid-ce7937a4-7fff-62eb-e54f-cb164a590257"><span>The import of users from </span><strong>Active Directory / OpenLDAP</strong><span> is done by clicking on the </span><span>Synchronize users from Active directory / OpenLDAP</span><span> button.</span></span></p> | ||
+ | <table border="0" width="111" height="24"> | ||
+ | <tbody> | ||
+ | <tr> | ||
+ | <td>[[Image:active_directory_5.png|none|740px|thumb|middle|link=http://wiki.meditex-software.com/images/active_directory_5.png|]]<br /></td> | ||
+ | </tr> | ||
+ | </tbody> | ||
+ | </table> | ||
+ | <p><span id="docs-internal-guid-1bf0ed4f-7fff-d52c-c0d5-87c2731f4cc3"> </span></p> | ||
+ | <p dir="ltr"><span>If a user already exists in MedITEX, MedITEX checks if he belongs to other groups and assigns it the according login rights.</span></p> | ||
+ | <p dir="ltr"><span>If a user doesn’t exist in MedITEX yet, MedITEX would create a new one during synchronization. Name, surname and title would be taken over from </span><strong>Active Directory / OpenLDAP</strong><span> to MedITEX. The username of the MedITEX user will be the same one from </span><span><strong>Active Directory / OpenLDAP</strong>.</span><span> MedITEX doesn't support all special characters though, as there are restrictions concerning the database username (Firebird username). In order to complete the import, new usernames without special characters must be created. These usernames will only be used internally and are not required for logging in. At the end of the synchronization, a list contains all users imported with special characters and a suggestion for the internal username (MedITEX username) is shown. Usernames can be customized in the list. Users will be able to connect to MedITEX using their Active Directory usernames with special characters.</span></p> | ||
+ | <p dir="ltr"><span>The easiest way would be to avoid special characters already in <strong>Active directory </strong>or<strong> OpenLDAP</strong>.</span></p> | ||
+ | <p dir="ltr"><span>The synchronization can take a while, because of the connection to the <strong>Active Directory / OpenLDAP</strong> server.</span></p> | ||
+ | <p><span>It is recommended that whenever a change is done on the </span><strong>Active Directory </strong><span>or</span><strong> OpenLDAP</strong><span> server (new users, updated groups, etc.), a synchronisation in MedITEX Administration should be done.</span></p> | ||
+ | <p>The users which are imported need to be placed in to a group. </p> | ||
+ | <p>A single user can not be imported. An arbitrary amount of users can also not be imported. </p> | ||
+ | <p>All users imported from OpenLDAP for a given subtree (specified by the BaseString parameter) must have a unique ID. </p> | ||
+ | <p>If there is a migration from <strong>Active Directory</strong> to <strong>OpenLDAP</strong> (or vice versa) the existing <strong>Active Directory</strong> users must be handled accordingly or set to inactive.</p> | ||
+ | <p>Using SSL for <strong>OpenLDAP</strong> is not supported.</p> | ||
+ | <p> </p> | ||
+ | <p> </p> | ||
<table style="float: right;" border="0"> | <table style="float: right;" border="0"> | ||
<tbody> | <tbody> |
Latest revision as of 14:59, 27 February 2020
Contents |
Buttons
Buttons with a blue dotted frame have special functionalities. Click on it to have more information.
<a href="/index.php?title=Administration_of_staff_and_users#Enter_new_person_.2F_Change"><img style="display: block; margin-left: auto; margin-right: auto; border: 2px dotted blue;" src="/images/Plus.png" alt="" /></a> | New person: click here to add a new person to the list. |
<img src="/images/DeleteX.png" alt="" width="26" height="24" /> | Delete person: click here to delete the selected person from the list. Confirmation is required. |
<a href="/index.php?title=Administration_of_staff_and_users#Enter_new_person_.2F_Change"><img style="display: block; margin-left: auto; margin-right: auto; border: 2px dotted blue;" src="/images/ChangeButton.png" alt="" width="86" height="27" /></a> | Edit person: click here to edit information of the selected person |
Enter new person / Change
By double-clicking a row from the list, by clicking on "New person" or by clicking on "Change", this window will be displayed. Here you can add or edit information of the patient.
Buttons
<img src="/images/ChooseColour.png" alt="" width="150" height="28" /> | Choose colour: to add or change the label colour of this person. |
<img src="/images/ChangePassword.png" alt="" width="231" height="30" /> | Change password: this button only appears in case information of a person is being edited. |
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/EnterUsernameAndPAssword.png" alt="" width="232" height="29" /> | Enter username and password: this button only appears in case a person is being added. |
Tabs
User name: displays the username when editing a person. If a new person is being added, this field will be blank. Show in colour: this is the colour that will be displayed for this user throughout all MedITEX programs. Program language: language displayed to this user when MedITEX tools are started. External staff member: select this box for external members working for the clinic. Location: in case of multiple locations, this setting identify which one this user is allocated to. Leave if blank if this user should be visible in all locations. User has access to patient data from: in case of multiple locations, allows users to see patient data from all locations, not only to the one he/she is allocated to. Active: this check box allows this person to be selectable throughout program forms. For example: if Dr. Johnson does not have this box checked, he will not be able to be selected for a treatment. Function: type of work done by this person. Rights: these are the permissions of this person. |
<img src="/images/NewPersonContacts.png" alt="" width="540" height="682" /> |
Contact information about this person. |
<img style="display: block; margin-left: auto; margin-right: auto;" src="/images/howto48.png" alt="" width="48" height="48" /> | If you would like to get more information, please follow <a href="/index.php?title=MedITEX_Administration_how_to">this link</a> and check our How to page. |
Import/synchronization of users from Active directory
The import of users from Active Directory / OpenLDAP is done by clicking on the Synchronize users from Active directory / OpenLDAP button.
If a user already exists in MedITEX, MedITEX checks if he belongs to other groups and assigns it the according login rights.
If a user doesn’t exist in MedITEX yet, MedITEX would create a new one during synchronization. Name, surname and title would be taken over from Active Directory / OpenLDAP to MedITEX. The username of the MedITEX user will be the same one from Active Directory / OpenLDAP. MedITEX doesn't support all special characters though, as there are restrictions concerning the database username (Firebird username). In order to complete the import, new usernames without special characters must be created. These usernames will only be used internally and are not required for logging in. At the end of the synchronization, a list contains all users imported with special characters and a suggestion for the internal username (MedITEX username) is shown. Usernames can be customized in the list. Users will be able to connect to MedITEX using their Active Directory usernames with special characters.
The easiest way would be to avoid special characters already in Active directory or OpenLDAP.
The synchronization can take a while, because of the connection to the Active Directory / OpenLDAP server.
It is recommended that whenever a change is done on the Active Directory or OpenLDAP server (new users, updated groups, etc.), a synchronisation in MedITEX Administration should be done.
The users which are imported need to be placed in to a group.
A single user can not be imported. An arbitrary amount of users can also not be imported.
All users imported from OpenLDAP for a given subtree (specified by the BaseString parameter) must have a unique ID.
If there is a migration from Active Directory to OpenLDAP (or vice versa) the existing Active Directory users must be handled accordingly or set to inactive.
Using SSL for OpenLDAP is not supported.
<a href="/index.php?title=MedITEX_Administration_manual">Back to MedITEX Administration manual </a> |
<a href="#top">Back to top</a> |