Posts

In privacyIDEA 2.22 the flexibilty of using arbitrary user attributes in the RADIUS protocol was heavily improved. But there are a lot of other features and enhancements. You can find the complete article at privacyidea.org.

privacyIDEA Appliance

Our enterprise customers may now install and configure privacyIDEA as a privacyIDEA appliance, based on the Ubuntu 16.04 enterprise packages. This way customers get an additional flover in addition to the python package index, CentOS, RHEL, Debian and Ubuntu for running and maintaining privacyIDEA. The Appliance allows easy setup of MySQL Master-Master-Replication, RADIUS clients and Backup and Restore. It also helps to manage the Audit log.
You may read more about the privacyIDEA Appliance in our blog post or take a look at it in action in the youtube channel.

privacyIDEA 2.19.1 available on the Univention Corporate Server 4.2

The current enterprise version 2.19.1 of privacyIDEA is now available on the Univention Corporate Server 4.2. The last version on the Univention Corporate Server was 2.18.1. With version 2.19.1 privacyIDEA is also available on the new Release 4.2 of the Univention Corporate Server. Thus customers running privacyIDEA on UCS 4.1, may easily upgrade UCS to 4.2.
Read more about this in our blog.

privacyIDEA LDAP Proxy available

The privacyIDEA LDAP Proxy is now available as ready made product. The LDAP Proxy allows an easy integration of arbitrary native applications or web applications which only allow authentication via LDAP. This way no addition plugin is necessary. The privacyIDEA LDAP Proxy acts as broker between the application, the LDAP directory or Active Directory and privacyIDEA.
Read more about the privacyIDEA LDAP Proxy on our website.

Events

Pick your calendar and write down some dates for interesting upcoming events!
At the end of summer Friedrich Weber and Cornelius Kölbel will give a talk about the privacyIDEA LDAP Proxy at the FrOSCon conference. NetKnights is also exhibitor and sponsor of FrOSCon and you will be able to ask everything you ever wanted to know about privacyIDEA and especially two factor authentication with LDAP.
FrOSCon takes place on August 19th and 20th in St. Augustin at the University Bonn-Rhein-Sieg, Germany.
You may also take a look at Cornelius’ previous, enjoyable talks (German) “Alles meins!” and “Am Puls der Zeit” on Youtube.
In October 2017 NetKnights will be at the it-sa, the biggest German IT-Security fair in Nuremberg. NetKnights will also have a stand there. Read more about this in our blog post.

This year NetKnights will be at the IT Security Expo and Congress “it-sa” together with the partners bytemine and Rempartec.  it-sa takes place once a year in Nuremberg, Germany in autumn. This year it is October 10th-12th 2017. During the last years up to 500 exhibitors presented new services and products in the field of IT Security. it-sa attracts over 10.000 visitors every year.

News about NetKnights and privacyIDEA

Use this chance to also get all news about NetKnights and privacyIDEA first hand! Learn more about privacyIDEA Enterprise Edition, the privacyIDEA Appliance or the privacyIDEA LDAP-Proxy.

Visit us in Hall 10.1, stand 208 – right accross from Cisco Systems or make up your personal date!

Today we released privacyIDEA 2.19. Packages are available in the Launchpad-Repos for Ubuntu 14.04LTS and 16.04LTS. You can also install privacyIDEA on any Linux distribution using the python package index.

New Features in privacyIDEA

Authentication performance

privacyIDEA 2.19 is up to 72% faster!

In tests in the lab privacyIDEA 2.19 shows improved performance. Authentication requests are up to 72% faster than in the previous version. This is also due to a new generic user cache. This user cache stores the link between login name and user object in the local SQL database. Thus time consuming requests to the originial user store like LDAP servers or Active Directory get obsolete.

Filter U2F devices for the users

Using policies the administrator can define which type of U2F device the user is allowed to register. In further policies the administrator can also define, which U2F types the users can use to authenticate at certain applications. This way the usage of certain U2F devices can be denied in your company or certain devices from specific vendors can be required for login to sensitive systems.

Secure smartphone apps with privacyIDEA

The classical smartphone app enrollment comes with several problems, which privacyIDEA 2.19 can solve.

In a previous blog post we already pointed out the limitations of the usual smartphone enrollment with the Google Authenticator.  As a company or large organization you want to keep control over the enrollment processes of your users. Thus in version 2.19 of privacyIDEA a better rollout possibility was added. The smartphone and the privacyIDEA server do a mutual key generation. Both create a component, the secret key is generated from both components. This avoids easy copying of the QR-Codes.

Read more details in the privacyIDEA Blog.

More functions

Version 2.19 comes with further detail improvements like using the IP address or the browser user agent in the event handler framework. The date and timeformat was consolidated. Now the complete ISO date with timezone is saved to the database. This heavily eases working across timezones in international setups.

You may want to take a look at the complete Changelog.

Enterprise Edition and Consultancy

NetKnights provides consulting and support with the privacyIDEA Enterprise Edition. Using Open Source you optimize your total cost of ownership this way, that there are no external limitations which dictate how long or short your may use the software. Getting the privacyIDEA Enterprise Edition including an SLA you get the warranty and thus operating safety.

 

You want to stay tuned? Please subscribe to our newsletter!

You want to test the system yourself? Register for a test instance!

You want to know more? Get in touch!

Today privacyIDEA 2.18 was released. Packages are available in the launchpad respository for Ubuntu 14.04LTS and 16.04LTS. Using the Python package index privacyIDEA can be installed on any distribution.

privacyIDEA manages certificate authorities

The flexible Open Source multi-factor-authentication system privacyIDEA comes with new featues in regards to certificate authorities. In addition to OTP tokens, smartphones, email- and SMS-token, Yubikeys and Nitrokeys privacyIDEA has improved the managing capabilites of certificate tokens. The administrator can use a setup wizard to setup a local CA more easily. If a certificate token is revoked, the CRL will be created automatically. Using certificate templates it is easier for administrators and users to enroll the type of certificate which suites the best.

You can get more information from the privacyIDEA blog.

 

Further Enhancements

privacyIDEA 2.18 comes with a lot of further enhancements which will ease the work with your privacyIDEA installation. You should definitively take a look at the complete Changelog.

If your users are located in an LDAP directory you should check the settings of your LDAP resolver. The new version of privacyIDEA relies on a new version of the Python ldap3 module and the privacyIDEA can easily check the validity of the LDAP server certificate thus mitigating the risk of man-in-the-middle attacks.

Enterprise Edition

NetKnights provides consulting and support with the privacyIDEA Enterprise Edition. Using Open Source you optimize your total cost of ownership this way, that there are no external limitations which dictate how long or short your may use the software. Getting the privacyIDEA Enterprise Edition including an SLA you get the warranty and thus operating safety.

In order to secure the login process with two factor authentication in an application there are different approaches.

Two-Factor-Authentication via standard protocols and plugins

With privacyIDEA we used standard protocols like RADIUS and SAML. If the application that you need to protect can facilitate RADIUS or SAML, the validate of the second factor can be performed by the privacyIDEA RADIUS Server or by privacyIDEA acting as a SAML Identity Provider. In this case you only need to change the configuration of the application, but you do not need to change the application.

Other applications provide an authentication framework, where the authentication can be extended using plugins. For such scenarios many different plugins are available to connect the application to the privacyIDEA Authentication Server. As of know a long list of plugins is already available for applications like TPYO3, ownCloud, NextCloud, WordPress, dokuwiki, django, OTRS, Apache, NGINX, PAM/OpenVPN and also for authenticating at the Windows Desktop.

But some applications do not support RADIUS or SAML and also do not provide an authentication framework to add 2FA via a plugin. Sometimes simply time is short, to develop a plugin in the corresponding programming language.

privacyIDEA LDAP-Proxy

To also provide strong authentication also for those applications and authenticate the users with two factors against privacyIDEA, we develop the privacyIDEA LDAP-Proxy.

The privacyIDEA LDAP-Proxy can be used, if the application authenticates the users against an LDAP server like OpenLDAP or Microsoft Active Directory. The privacyIDEA LDAP-Proxy is plugged between the application and the originial LDAP server. The application is reconfigured, to not use the LDAP server for authentication anymore, but to authenticate users against the LDAP-Proxy. Now, the privacyIDEA LDAP-Proxy can authenticate the users and verify the the authentication against the privacyIDEA Server and use the original LDAP server to only fetch user data.

The two factor authentication is totally transparent for the user and for the application.

The advantage of the IT department is obvious: The originial LDAP server is not touched or modified. The program code of the application is not modified or exteneded. The application is only reconfigured within the limits of the intended possibilities and supported scenarios. To the application the LDAP-Proxy looks like a normal LDAP server. Thus you will not loose any warranty and support by the vendor of the application.

In contrast to two factor solutions, which are solely based on OpenLDAP, the privacyIDEA LDAP-Proxy has one big advantage. It will work with any kind of originial LDAP server, be it OpenLDAP, Microsoft Active Directory or Samba.

Example Scenario

In our example scenario we look at the login at SuiteCRM. SuiteCRM is an Open Source Customer Relation Management solution. There are no two factor plugins for SuiteCRM. But SuiteCRM authenticates it’s users against LDAP. So we will configure SuiteCRM to authenticate the users against the privacyIDEA LDAP-Proxy to add transparent two factor authentication to SuiteCRM.

We could also look at any other application, which authenticates users against an LDAP server. But SuiteCRM suites us well. We install SuiteCRM on the Univention Corporate Server. The installation of the application works like a charm, SuiteCRM is nicely configured against the Univention Corporate Server Domain Controller – the original LDAP server. This is just to have the test scenario up and runing in a few minutes.

We can install the privacyIDEA Authentication Server on any Linux distribution or we can also install the privacyIDEA Server on the Univention Corporate Server. privacyIDEA is also contained in the Univention App Center and can be installed on the UCS within a few minutes. Then privacyIDEA is setup against the users in the Univention LDAP server automatically and the administrator only needs to enroll or assign tokens like Yubikeys, OTP tokens or smartphone apps to the users.

SuiteCRM will be configured this way, that it does not connect to the UCS LDAP server but to the privacyIDEA LDAP-Proxy.

If needed several of the components can be installed on one single system.

Integration

LDAP-Proxy installieren und konfigurieren

The privacyIDEA LDAP-Proxy is currently available via Github in a beta version. It is developed based on Python and Twisted. Thus there are many different ways for the deployment. All necessary configurations are done in configuration file once.

The administrator needs to tell, were the original (UCS) LDAP server and the privacyIDEA instance are located. In the SuiteCRM setup an additional LDAP service account is needed, which the administrator also adds to the configuration file.

For more detailed information see the file README.md.

To start the LDAP proxy run

twistd -n ldap-proxy -c config.ini

In a productive environment you would start the LDAP proxy automatically as a service via systemd. The configuration file config.ini can be stored at the location of your choice. The file example-proxy.ini contains a lot of comments, which explain all possible configuration settings.

The configuration file

The administrator needs to adapt the following configuration settings:

The parameter instance in the section privacyidea determines, where the LDAP proxy can contact the privacyIDEA Authentication Server.

The administrator needs to define the connection to the original LDAP server in the section ldap-backend including IP address or FQDN and the protocal being LDAP, LDAPS or LDAP+STARTTLS

The parameter endpoint in the ldap-proxy section also contains the information on which port the original LDAP server is listening.

Finally the administrator needs to configure the LDAP attribute which contains the loginname. This can be done using the paramter attribute in the sections user-mapping.

The service account allows common LDAP searches

Simple applications, which only verify the user with a user bind do not need any additional settings. However, SuiteCRM uses an additional service account for common LDAP searches. The administrator needs to add this service account in the section ldap-proxy with the parameter passthrough-binds and in the section service-account.

Configure SuiteCRM

In SuiteCRM the administrator only needs to reconfigure the LDAP server. Go to the Admin-Menu which can be reached in the upper right corner.

Choose Password Managemant.

Here you can configure the LDAP server. Enter the FQDN or IP address of the new LDAP proxy.

Done.

Conclusion

The SuiteCRM user is now authenticated via the LDAP proxy against privacyIDEA. The complete password entry is sent to privacyIDEA for validation. The user has to enter his static (probably LDAP password) and the OTP value. Thus you can also do smooth migrations since this looks the same to the user.

Which device (2nd factor) the user has to use for authentication is completely centrally defined by privacyIDEA. The administrator can also assign different device types to the users. Some users can authenticate with Yubikeys, others with OTP tokens or OTP cards, some with a smartphone app like the Google Authenticator and some users may get their login code via SMS or Email.

We will continue developing the LDAP-Proxy and we are looking forward to any feedback. If you want to stay updated watch the Github repository or subscribe to our newsletter.