The VOGO identity engine
Accounts, passwords, sessions, the second factor, roles and groups.
VOGO eBS Identity Server
VOGO-IS — VOGO Identity Server, the identity server of the VOGO eBS suite. It holds the accounts, checks who signs in, with the second factor, and opens all of the organisation’s applications after a single sign-in.
Built on the VOGO identity engine, with Keycloak and WSO2 Identity Server as libraries for federation and standard protocols.
Employees, citizens and partners each have their account, in a single identity system. The VOGO engine holds the accounts, sessions, roles and groups and asks for the second factor at every sign-in.
The organisation’s applications — VOGO eBS, the portal, the mobile app, the financial applications, BI — connect through OpenID Connect, OAuth 2.0 or SAML 2.0. A person signs in once and opens all of them.
Accounts can also come from other sources: the organisation’s directory, Microsoft Entra ID, partners’ identity providers and ROeID for citizens. VOGO-IS federates them and gives them the same access rules.
Identity. Authentication. Federation. Control.
Accounts, passwords, sessions and sign-out, on the VOGO identity engine.
Google Authenticator or an e-mail code, mandatory or risk-based, per application.
A single sign-in for all connected applications, with single sign-out.
OpenID Connect, OAuth 2.0 and SAML 2.0, for new and existing applications.
The organisation’s directory (LDAP, Active Directory), Microsoft Entra ID, partners and ROeID.
Roles are given through groups; rights on menus and operations, in the same administration.
Applications authenticate with each other through OAuth 2.0 client credentials, without shared passwords.
Every sign-in, failure, lock-out and reset, with the account, the time and the address.
Accounts, sessions and the second factor run on the VOGO eBS identity engine, already used in the application.
Federation and the standard protocols use two mature libraries, chosen per identity provider.
Citizens will sign in through ROeID, with the account created automatically at the first sign-in.
Failed sign-ins, lock-outs and access from new devices reach VOGO eBS SIEM.
Support, updates and training are provided by VOGO, as the product’s manufacturer.
Accounts, passwords, sessions, the second factor, roles and groups.
Issuing and validating OpenID Connect and OAuth 2.0 tokens and SAML assertions.
The links with the organisation’s directory, Microsoft Entra ID, partners and ROeID.
Users, roles, groups and rights on menus, in the VOGO eBS IAM screens.
Identity providers, connected applications and security events, in Romanian.
The product uses as mature open-source libraries: Keycloak and WSO2 Identity Server.
VOGO eBS Identity Server (VOGO-IS) is the identity server of the VOGO eBS suite: it holds the accounts, checks the sign-in with the second factor and opens all of the organisation’s applications after a single sign-in.
The VOGO engine covers accounts, sessions and access. For federation and protocols, each identity provider is connected through the library that suits it: Keycloak for directories and portals, WSO2 Identity Server for enterprise and institutional federations.
Yes. VOGO-IS is an integrated product, developed, licensed and supported by VOGO, with the VOGO engine, modules, console and support. The product uses as mature open-source libraries: Keycloak and WSO2 Identity Server.
On premise, in the organisation’s infrastructure. Accounts and authentication data never leave it.
Request a demo on your organisation’s applications and accounts.
Note: The services are provided in line with the European DNSH principle – “Do No Significant Harm”, in accordance with Article 17 of Regulation (EU) 2020/852 on the establishment of a framework to facilitate sustainable investment and with the European Commission’s technical guidance on the application of the DNSH principle, C/2023/111.