Univention Bugzilla – Bug 47895
Improve first-time experience of "User import" UMC module
Last modified: 2023-06-23 13:15:51 CEST
Created attachment 9687 [details] User import error pop-up "No permissions for running an import for any school." Not sure if this is the correct component, feel free to change if not. I've set up a DC master on 4.3-0, upgraded to 4.3-1, installed UCS@school, upgraded to 4.3-2 and installed the new import module: univention-install ucs-school-import-http-api univention-install ucs-school-umc-import univention-remove ucs-school-umc-csv-import When I access the User import module in the UMC I get an error pop-up (see attachment): An error occurred Could not fulfill the request. Server error message: No permissions for running an import for any school.
I think the pop-up should be changed to look less like an error and more like a notification that there are no users permitted to do an import. Such as the pop-up that appears when one tries to create school users without having created a school yet or opening the computer room module without having configured any rooms.
This is documented in the internal documentation (see https://billy.knut.univention.de/~dtroeder/http-api-doc/import-permissions.html). An official doc doesn't exist yet. But I concur, that a freshly installed software should be less rebuffing. We have discussed yesterday to make the message more helpful (something like "read article <TODO> to grant access permissions for this module"). I'm changing the title accordingly. Alternatively we could simply always grant the group "Domain Administrators" (or only the user "Administrator") access. They can get it anyway and it would be consistent with the access permissions to other school wizards.
(In reply to Daniel Tröder from comment #2) > We have discussed yesterday to make the message more helpful (something like > "read article <TODO> to grant access permissions for this module"). I'm > changing the title accordingly. > > Alternatively we could simply always grant the group "Domain Administrators" > (or only the user "Administrator") access. They can get it anyway and it > would be consistent with the access permissions to other school wizards. But on a freshly installed system, access to the UMC module is not sufficient since the corresponding import configuration is also missing. Currently I think the best solution would be a message that states that this module/import method is not configured yet and has to be configured first. The message should contain a reference to the HTTP API import manual and/or a link to a quickstart guide.
A proposal to improve the user guidance here: - Create a 'quickstart guide' in the Knowledge Base on help.univention.de that also includes a csv file with ready to try import data - Add Administrator to all OU-import-all groups per default - cp /usr/share/ucs-school-import/configs/ucs-school-testuser-http-import.json /var/lib/ucs-school-import/configs/demoschool.json per default on new installations of the User Import. This way the import for the demoschool with data from the httpapi testuser generation works ootb with the demoschool
(In reply to Ole Schwiegert from comment #4) > A proposal to improve the user guidance here: > > - Create a 'quickstart guide' in the Knowledge Base on help.univention.de > that also includes a csv file with ready to try import data http://docs.software-univention.de/de/ucsschool43.html There is already a "Quickstart Guide" for UCS@school. I think, either we add a new document "UCS@school-Quickstart-Guide für graphischen Benutzer-Import" or we add a new section to the document "UCS@school-Handbuch für graphischen Benutzer-Import" > - cp > /usr/share/ucs-school-import/configs/ucs-school-testuser-http-import.json > /var/lib/ucs-school-import/configs/demoschool.json per default on new > installations of the User Import. This way the import for the demoschool > with data from the httpapi testuser generation works ootb with the demoschool I'm not sure we want to take this step automatically. The config for the HTTP API/UMC module "User import" conflicts with the config for the regular CLI import. I.e. only one of both is possible at a time.
(In reply to Sönke Schwardt-Krummrich from comment #5) > (In reply to Ole Schwiegert from comment #4) > > A proposal to improve the user guidance here: > > > > - Create a 'quickstart guide' in the Knowledge Base on help.univention.de > > that also includes a csv file with ready to try import data > > http://docs.software-univention.de/de/ucsschool43.html > There is already a "Quickstart Guide" for UCS@school. I think, either we add > a new document "UCS@school-Quickstart-Guide für graphischen Benutzer-Import" > or we add a new section to the document "UCS@school-Handbuch für graphischen > Benutzer-Import" > I will draft a proposal for a quickstart guide for wherever we put it. THe Knowledge Base was proposed because it is easier to also provide a file for download there instead of using our download mirror. > > - cp > > /usr/share/ucs-school-import/configs/ucs-school-testuser-http-import.json > > /var/lib/ucs-school-import/configs/demoschool.json per default on new > > installations of the User Import. This way the import for the demoschool > > with data from the httpapi testuser generation works ootb with the demoschool > > I'm not sure we want to take this step automatically. The config for the > HTTP API/UMC module "User import" conflicts with the config for the regular > CLI import. I.e. only one of both is possible at a time. Then the question here is which is our primary way of importing Users. As I understood we want to promote the new "User Import" and not the 'old' one. Also this would only change the behavior(config) when importing for the DEMOSCHOOL and make it compatible to the HTTPAPI-Import for which we can generate testdata easily. Since I would not overwrite the default config the behavior would not change for any other school but DEMOSCHOOL
This issue has been filed against UCS 4.3. UCS 4.3 is out of maintenance and UCS components may have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.