The UCS 4.1 release includes the recent Samba version 4.3.1. In this article, I like to address the improvements and new features of this Samba update and their implementation in UCS 4.1.
With Version 4.1 of Univention Corporate Server Univention is integrating a service into Univention Corporate Server which makes life easier for users and administrators alike: the Univention Self Service modules. These allow users to change their saved passwords autonomously (without administrator involvement).
The release 4.1 of Univention Corporate Server brings some new important features for even more secure and convenient use. For example, the Univention App Center now also supports apps which use the container technology Docker. Also new is the integrated global single sign-on mechanism which can be rendered even more secure via the use of two-factor authentication. Another particular highlight are self-service mechanisms whereby users can reset their passwords autonomously.
Version 4.1 of Univention Corporate Server supports Docker Apps from within the App Center. However, firstly lets have a look back on how the App Center has developed over the last years to better explain the reasons why we decided to support Docker. Afterwards, we will have a quick look at the technical details of the implementation within UCS before discussing what the advantages for app vendors and, most importantly, users are. Lastly, I will be happy to give a quick peek into what the future has in store for the App Center.
In order to be able to guarantee the seamless integration of apps in the identity management system provided by UCS even more proficiently, we have now implemented a single sign-on for UCS function in Version 4.1. of Univention Corporate Server. Single sign-on allows a user who has authenticated himself once on an identity provider to use a wide variety of other services without the need to sign on to each of these additional services individually.
We are pleased to announce the availability of UCS 4.0-4 for download, the fourth point release of Univention Corporate Server 4.0.
It includes all errata updates issued for the previous version 4.0-3. Beside various enhancements and bugfixes, it contains important improvements with regard to the Active Directory compatibility and the UCS management system.
We are pleased to announce the availability of the release candidate of UCS 4.1 as DVD-ISO for amd64. Information on download and installation can be found in the Univention Wiki in the article UCS 4.1 Development – Testing. Further information on the time schedule can be found in this article as well.
How can companies make access to their networks and applications securer and more user-friendly at the same time? What’s behind the terms SAML, multiple-factor authentication and single sign-on in this context? Cornelius Kölbel, Managing Director of our partner NetKnights, took the time to explain these technologies to us and illustrate how you can use the multiple-factor authentication solution privacyIDEA and SAML to set up a secure network on UCS plus saving employees time when signing in.
In “Fail-safe performance and load distribution thanks to LDAP replication” I focused on describing the UCS OpenLDAP directory service. Unfortunately, OpenLDAP is only of comparatively little help to me if I want to operate Windows systems in my network, as Windows doesn’t speak the standard-compliant LDAP protocol as a rule, but rather a particular dialect that Microsoft selected for its Active Directory. I would now like to explain which technologies integrated in Univention Corporate Server we can use to deal with this situation and go into more detail about the replication via listener/notifier for OpenLDAP, DRS replication for the Active Directory and the “Univention S4 Connector”, which synchronises between the two worlds.
We have now been using git as the version control software for our projects in the Professional Services Team at Univention for a number of weeks and to great success. In this blog article, I want to give you a bit more information about our decision to employ git, report on our initial, recent experiences and provide a perspective of the aspects still requiring work. In doing so, I hope maybe to provide you with a suggestion or two for your own projects or that perhaps you will also have ideas for how we can implement our requirements even better using git.
TL;DR
