HTGSOFT/SSO solution
ACCOUNT SOURCES

One identity source.Consistent updates.

Connect existing directories or account sources managed in HTG ID. Mapping and synchronization rules help businesses retain clear identity ownership.

Explore features
  • Directory sources
  • Attribute mapping
  • Synchronization rules

FROM SEPARATE ACCOUNTS TO UNIFIED IDENTITY

Convenient sign-in. Controlled administration.

When every application has its own account, staffing changes can involve many manual steps. SSO creates a shared authentication point, combined with clear access-granting processes in each application.

01

Single sign-on

Use a shared sign-in session to access integrated applications, reducing repeated password entry in everyday work.

02

Open-standard connections

Integrate through OpenID Connect or SAML where supported; check configuration, sign-in, and sign-out flows before operation.

03

Authentication policies

Configure MFA, password policies, and access sessions according to user groups, sensitivity, and the agreed plan.

04

Roles & user groups

Organize users into groups and map roles to applications. Detailed business permissions are checked in the receiving system.

05

Identity source integration

Assess connections with LDAP, Active Directory, or existing identity providers, with suitable attributes and synchronization mechanisms.

06

Access lifecycle management

Define account creation, change, and locking processes; monitor sign-in events and hand over administration guidance to internal teams.

CORE FEATURES / HTG ID

Manage identity from account sources to every application.

Explore four layers of an SSO system: identity sources, application connections, authentication policies, and the access lifecycle. Each layer connects to a specific operational situation.

CORE FEATURES / 01

Maintain a clear source of identity information.

Bring together users from existing directories or account sources managed in HTG ID. Design attribute mappings and synchronization rules to avoid creating multiple identities for the same employee.

  • Connect LDAP / Active Directory or a suitable identity source
  • Map user IDs, display names, email addresses, and units
  • Define authoritative data sources and duplicate-account rules
  • Choose read, update, and synchronization modes for each source
Practical value

Account information has clear ownership and consistent update rules.

ACCOUNT SOURCES

One identity source. Consistent updates.

Directory sourcesAttribute mappingSynchronization rules
IMAGES & CONTEXT

Explore capability groups.

The connections between people, data, and work within the solution.

BRINGING THE SOLUTION INTO EVERYDAY WORK

A view through concrete situations.

01HR · IT · Application administrators

New employees accessing multiple systems

The challenge
An employee needs access to collaboration tools and business applications, involving several separate provisioning steps.
How to apply it
Identify the primary record source, working groups, and application list; provision accounts through integrated mechanisms, then check permissions in each system.

Users start work with a clear handover checklist.

02Unit managers · IT

Role or department changes

The challenge
Permissions from the previous role may remain while the new role requires additional access.
How to apply it
Update groups and roles according to the agreed matrix, check permissions received by applications, and record who confirms the change.

Access rights are reviewed against the new job role.

03Development teams · Identity administrators

A new application joins the ecosystem

The challenge
New software needs shared sign-in, but its permission and session mechanisms may differ from existing applications.
How to apply it
Check OIDC/SAML, attributes, and redirect addresses; test sign-in, insufficient permissions, session expiry, and sign-out before opening access to users.

Add applications against a repeatable set of test criteria.

INTEGRATION ROADMAP

Connect each application. Verify every flow.

Start with priority applications and user groups, then expand according to compatibility and test results.

01

Map the current identity landscape

Review applications, account sources, supported protocols, and permissions. Agree on a pilot application, fields to map, and each party's responsibilities.

  • Application & account inventory
  • Agreed integration scope
SUITED TO YOUR ORGANIZATION

The right needs. The right context.

01

Businesses using multiple applications

Suitable when employees frequently switch between internal portals, business applications, and collaboration tools that support SSO integration.

02

Organizations with existing identity sources

Connect existing directories according to the assessment plan, helping reduce duplicate entry and clarify ownership of account information.

03

Application development organizations

Standardize authentication connections for new applications while retaining business permissions and data-control responsibilities within each system.

HTGSOFT SUPPORT

Designed around your business's application portfolio.

HTGSOFT conducts an assessment before finalizing Keycloak architecture, account sources, and integration order. Application provisioning, data synchronization, and session revocation capabilities are determined separately for each connection.

01

Applications, protocols & integrated flows

02

Identity sources, MFA, roles & account lifecycle

03

Infrastructure, backups, monitoring & operational responsibility

ANSWERS BEFORE YOU BEGIN

The details you
want to clarify.

Define the right scope for your organization together.

Can every application integrate with SSO?

Integration depends on the application's protocols and sign-in mechanisms. HTGSOFT prioritizes OIDC or SAML with compatible software; legacy systems may need source-code changes, connectors, or a separate approach after assessment.

Can existing accounts and directories be used?

Connections to LDAP, Active Directory, or other identity providers can be assessed. Define authoritative data sources, mapped attributes, duplicate-account rules, and change management before deploying synchronization.

Does SSO replace permissions and account management in every application?

SSO centralizes authentication and can provide role information. Applications must still enforce business permissions. Automatically provisioning accounts, locking access, or ending sessions in each application requires corresponding integrations and testing.

Consultant beside work equipment
Start a conversation

Your challenge.HTGSOFT helps make the connections.

Share your software, collaboration, infrastructure, or hardware design needs. Together, define an implementation approach suited to your organization.

CONSULTATION REQUEST

Let's start with your needs.

Start a conversation

Experience HTGSOFT solutions

Share your needs so HTGSOFT can review them and discuss an implementation approach.

Explore the ecosystem

What solution are you looking for?

HTGSOFT

Solution information

Product interface

Explore how the solution connects people, data, and work.

Product interface image with data processed
HTGSOFT
YOUR PRIVACY

Cookie preferences

Choose storage categories or read the privacy or cookie policy. Optional choices are off by default.

You decide which optional categories to allow.

Select the categories you want to allow, then click “Save choices.” You can reopen this panel from the Cookie icon or the link in the footer.

Your choices: the switches remember which categories are allowed. The website currently has no integrated analytics or marketing services.

HTGSOFT
HTGSOFT

Terms of Use

WEBSITE TERMS OF USE

Communicate clearly, use responsibly.

Updated on 16/11/2026

Content scope

The website provides information about HTGSOFT's capabilities, products and services and receives consultation requests. Deployment scope, configuration, pricing, schedules and service commitments are defined in formal proposals or agreements between the parties.

Submitting consultation requests

You are responsible for providing accurate information and having the right to use the information submitted. Send only data needed for the discussion; do not include passwords, access codes, payment information or unnecessary sensitive data in your request.

Request acknowledgment and handling

The acknowledgment confirms only that the system recorded your information when submission completed. Receiving a request does not automatically create a contract, order or service commitment. HTGSOFT uses contact information to discuss and clarify an appropriate scope.

Content ownership and permitted use

Website content, design and brand marks belong to HTGSOFT or their respective owners. Copying, reuse or exploitation must respect owners' rights. Do not use the website to submit unlawful content, disrupt services or attempt unauthorized data access.

Privacy and cookies

Contact information is processed according to the Privacy Policy; browser storage choices are described in the Cookie Policy. You can open these policies from the footer or Cookie button.

Contact

Questions about website use or consultation requests can be sent to info@htgsoft.com or call 028 7105 6839.
WORKING WITH HTGSOFT

HTG.iPilot

AI consultation assistant

Checking AI connection…

START WITH YOUR NEEDS

Find a connected approach together.

Discuss products, digital transformation, or system operations. You can also leave your details for a direct consultation with HTGSOFT.

0/1800 characters · Shift + Enter for a new line

You can clear the conversation at any time.