The UCS@school team released the 4th version of the UCS@school app a few weeks ago. It is technically based on UCS 4.4 and brings some new functions as well as various adjustments and improvements.
In this article, I would like to give you a short overview about the most important new features for administrators and users, especially in the exam mode, computer room and laptop class control, single sign-on and printer control. Very interesting is the new ID-Connector, which enables data transfer between federal state directories, school district directories and school directories.
Identities and roles in a Microsoft Azure AD environment can be provisioned very easily thanks to the Office 365 Connector App for UCS. Users can get an easy single sign-on access to Office 365 resources while maintaining control over the information conveyed about each identity.
Moreover, in a UCS environment, precise permissions are often defined to control the visibility of user properties within an organization. Especially in large environments it is necessary that not every user “sees” every other user. For example, the data protection requirements at schools are implemented by UCS@school: The school authorities can administer user accounts centrally across all schools, but users only “see” each other within their own school. In a single Azure AD, such a separation is generally not provided, but the creation of several Azure AD or tenants is expected.
In this article I am going to explain how you can implement such separate setups with UCS for Azure AD more easily and how the scenarios are structured since the last update of the Office 365 Connector App.
As always, the errata updates of the past months have resulted in many small and large innovations, which we have collected and released with the release of UCS 4.4-3. I would like to give you an overview of the most important new features and an outlook on what we are currently working on. Important new features include better checking of required resources during installation, avoidance of Windows Explorer crashes with extended file system permissions, documentation of best practices in dealing with Windows printer drivers and printer settings, and improvements to the Samba 4 Connector.
After receiving so much positive feedback on our questions in the article “UCS 5.0 is coming!“, I’d like to use this article to ask you a few questions that are relevant to the further development of UCS 4 and the direction UCS 5 will take. We highly value the UCS user‘s opinion and like to hear what you have to say – use the comment box below or gladly write to firstname.lastname@example.org.
The Maintenance for the Core Edition version of UCS 4.3 has expired. Users using the Core Edition of UCS 4.3 should update to a more recent version of UCS to further receive security updates, bug fixes and minor releases.
Information about the new features of UCS 4.4 can be found in our blog article UCS 4.4 Release – Admin Diary, Self Services and Windows Domain Trusts.
A description of the steps necessary for the update can be found in the blog article How To: Upgrade to new UCS version 4.4.
Customers with a valid subscription contract for UCS are not affected and will receive updates until the end of March 2020 at least. More information about the Maintenance Cycle for UCS can be found in our Wiki article Maintenance Cycle for UCS.
I assume in the HowTo that a functional UCS Master already exists. I run this virtualized using Proxmox. I use a second VM for the terminal server environment.
The following steps are described in detail in this HowTo:
- Prepare LinuxMint with xRDP
- Installing and configuring privacyIDEA and RADIUS on the UCS Master
- Integrate xRDP with privacyIDEA
- Install and configure Guacamole with RADIUS Plugin
It’s been almost 5 years since we released UCS 4.0. During this time, UCS has evolved a lot. At the same time, we’ve continued to maintain the old version’s features. While most of them are popular with our users, others are not. There are also some things we would do differently if we had to do them again. By jumping to the next major version, we would like to get rid of some relics and implement several new features at the same time. We’re still at the very beginning, so not all decisions are final yet – but true to the motto “be open” I would like to share some of our ideas and plans in this blog post.
Final Version of the UDM REST API
Looking back at the first point release (UCS 4.4-1 in June 2019), our REST API for the Univention Directory Manager was still in beta stadium. Good news: the interface for accessing the directory service is stable now. The API connects applications to the UCS directory service; access is granted via a web service using HTTPS, and data is exchanged JSON format. So, the REST API offers the same functionality as the udm command line tool.
For example, it simplifies the maintenance of user properties or computer objects from connected systems. Developers of applications offered in the Univention App Center also benefit from the new, standardized access because they are no longer limited to the UDM Python interface. The REST API of the Univention Directory Manager is by default activated on all UCS 4.4-2 DC Master and DC Backup instances.
On the evening of September 6th, a vulnerability in the App Center repository server became known that allowed Docker images to be manipulated for Docker based apps. The vulnerability was in the Docker registry for the Univention App Center and allowed anonymous push of Docker images. The problem was fixed the following day by locking the anonymous push again.