The single sign-on system of Igor Sikorsky Kyiv Polytechnic Institute now supports the open OpenID Connect standard. Electronic Campus and My KPI are the first services to move to the new protocol.

KPI ID (auth.kpi.ua) is the single sign-on for the services of Igor Sikorsky Kyiv Polytechnic Institute. More than 20,000 students and 2,000 teachers use it to sign in to Electronic Campus, My KPI and other university systems. Identity can be confirmed in several ways: with Diia.Signature, BankID or a corporate Google account.

KPI ID now supports the OpenID Connect protocol. It is an open international authentication standard, the one behind "Sign in with Google" and "Sign in with Microsoft", among others. Supporting it makes connecting new services to KPI ID simpler: developers can use ready-made libraries, and popular platforms connect through their standard settings.

What OpenID Connect is

When a service offers "Sign in with Google", it does not check the user's password itself. It hands that task to Google and receives in return a confirmation of who has signed in. The rules by which the service and the sign-in provider exchange this information are described by the OpenID Connect standard.

The standard is open and widespread, so most programming languages, web frameworks and off-the-shelf products support it. If a sign-in provider works over OpenID Connect, connecting to it comes down to a few settings: the provider's address, the service identifier and a secret key.

This is now exactly how KPI ID works. For a service it becomes a sign-in provider like Google or Microsoft, only with university data and the sign-in methods accepted at KPI.

Why we added the standard

The idea came from practice. Teams building services for the university asked for OpenID Connect support: many of them had already worked with the standard in other projects and wanted to use the familiar tools for integration with KPI ID too.

At the same time, KBIS is deliberately moving its systems towards open standards. Standard solutions are easier to maintain and develop, developers know them well, and proven tools already exist for the common tasks. OpenID Connect support in KPI ID is one step in that direction.

What it gives

Developers. An integration with KPI ID can be built on a ready-made OpenID Connect library for your programming language. The library fetches the KPI ID settings from its address, redirects the user to sign in, verifies the response and returns the user's data. The integration page has ready examples for Node.js, C#, Python and PHP.

Off-the-shelf platforms. Systems that already speak OpenID Connect connect to KPI ID through configuration. For Moodle it is the auth_oidc plugin, for WordPress the OpenID Connect Generic Client plugin. Other products that support the standard connect the same way.

Users. Signing in stays the same: the "Sign in with KPI ID" button, a choice of how to confirm your identity, and you are in the service. If a person has already signed in to KPI ID, they will not see the sign-in page again: KPI ID returns them to the service straight away. That is how single sign-on works: confirm your identity once and move between university services without authenticating again.

How it works for the user

  1. The user clicks "Sign in with KPI ID" on the service's website.
  2. The service redirects them to the KPI ID sign-in page.
  3. The user chooses how to sign in: Diia.Signature, BankID or Google.
  4. KPI ID returns the user to the service, and the service receives a confirmation of the sign-in.
  5. The service opens with the user already signed in.

Services connected to KPI ID are also listed in the catalogue at auth.kpi.ua. A service opened from there receives the user already signed in.

Services that need the user's identity to be confirmed by the state can enable trusted identification mode. In this mode the sign-in page offers only Diia.Signature and BankID.

Campus and My KPI are already on the new protocol

Six university services work through KPI ID today. The move to the new protocol started with the ones used most. Electronic Campus, where students see their grades and records and teachers keep track of progress, already works with KPI ID over OpenID Connect. So does My KPI, where timetables are built, courses are chosen and individual study plans are kept.

Other services connected to KPI ID include KPI Sign, the platform on which the university concludes and signs contracts, in particular during the admission campaign. Projects created outside KBIS connect to KPI ID as well. For example, Vote OSS, a student project for electronic voting in student self-government elections, uses KPI ID so that only KPI students can vote.

What comes next

The move to OpenID Connect will happen in stages. Services connected to KPI ID over the previous protocol keep working as before. The previous protocol will be switched off only once every service has moved to OpenID Connect. New services connect to KPI ID over OpenID Connect.

The full guide with the settings, code examples for Node.js, C#, Python and PHP, and a walkthrough of the common mistakes: auth.kpi.ua/en/integration.

To register or connect a service, contact KBIS.

← Back to the blog