Intro

This manual page is mainly for area owners, key customer contacts, but also for end-users so that they can be aware of such solution and can ask management or proper ICT contacts to implement it also in their environment.

TDS platform does not need any external users source as it has it own identity with users database. Every TDS user has account in TDS with his own password and can enable MFA/2FA for better security.

However if organisations would like to make life easier for users by allowing them to be singned-in/authenticated seamlessly just by clicking "OrganisationX AzureAD" button instead of entering credentials, they can decide to integrate TDS platform into AzureAD or similar kind of identity provider.

Azure AD integration with TDS Keycloak using OpenID Connect

This is quite straightforward and modern solution for adding support for centralised authentication. We usually meet together with customer organisation representatives and their identity provider administrators and settle down procedure details and requirements. Then AzureAD adminstrators need to follow steps how to integrate TDS Keycloak using OIDC as defined in this chapter.

Registering application in Azure portal

Azure portal is expected to be used: https://portal.azure.com/#home

  • Go to https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps
  • Click "New registration"
  • Set name "Tietoevry DevOps Space (TDS) Keycloak" or something similar
  • Select who can use it, usually first option "Accounts in this organizational directory only (for example Tietoevry only - Single tenant)" is OK
  • Set Redirect URI to callback URL:

    https://identity.core.tds.CUSTOMERX.com/auth/realms/tds/broker/main-oidc/endpoint

    It says that it is optional, but it is mandatory in our case.

  • Click "Register"
  • On shown overview screen you shall find and copy following values that will be needed later for setup on Keycloak side:
    • Application (client) ID
    • Directory (tenant) ID
  • Following claims need to enabled:
    • sAMAccountName (onpremisessamaccountname)
    • email
    • firstname
    • lastname
  • AzureAD team must run following powershell commands to properly enable "sAMAccountName" claim

Providing information to TDS team

TDS team needs following details in order to finish integration:

AttributeExample/template value
Authorization URLhttps://login.microsoftonline.com/<TENANT-ID>/oauth2/v2.0/authorize
Token URLhttps://login.microsoftonline.com/<TENANT-ID>/oauth2/v2.0/token
Client IDb1a10f18-5456-47c3-9843-d90cd58c5278
Client Secret

m4yg87DR-_juvp~Tv4U9w-q9x8Mzmo~1Lp

Please make secret valid for as long applicable period as possible - infinity or maximum number of months that organisation allows.

We also need to setup process for replacing secret on regular basis according to validity possibilities.

TDS team then takes over and finishes setup according to internal documentation OpenID Connect brokering setup#Keycloakpart.

ADFS integration with TDS Keycloak using SAML

This solution is not as popular as AzureAD, but it is still possible to integrate this way if there is no other way. It is less flexible than OIDC as it requires proper timing of certificates exchanges when multiple teams/parties must organise themselves in corporate environments. From this point of view OIDC integration is recommended as it is quite easy to setup and it is more flexible than ADFS with SAML. Although OIDC requires regular exchanging of secrets, thanks to possibility to have multiple secrets at the same time, changes are very easy and do not require strict timing like in SAML case when certificates are being exchanged.

Also setup is less straightforward than in OIDC case. In case of need we provide consultancy.

  • No labels