apoupard/connect-im

IM is a service for Identity and Access Management. It is built upon a Keycloak instance.

IM

---

Description

IM is a micro-service for Identity and Access Management. It is built upon a Keycloak instance.

It allows you to create and manage: Users, Organizations and Roles. These Users and Organizations can then be used to authenticate to a Keycloak instance.

Architecture

IM interacts with Keycloak using Keycloak’s Admin Client. IM also exposes entrypoints to allow communications with any applications.

Getting started

IM works with a running Keycloak instance. It can easily be deployed as a docker container, within a docker-compose file: (link to docker repo)

version: "3.7"
services:
  im-gateway:
    image: smartbcity/im-gateway:${VERSION}
    container_name: im-gateway
    environment:
      server_port: 8004
      i2_issuers[0]_uri: ${ISSUER_URI}
      i2_issuers[0]_authUrl: ${KEYCLOAK_URL}
      i2_issuers[0]_realm: ${KEYCLOAK_REALM}
      i2_issuers[0]_clientId: ${CLIENT_ID}
      i2_issuers[0]_clientSecret: ${CLIENT_SECRET}
    ports:
      - "8004:8004"

Functionalities are divided into 3 entities: User, Organization and Role.

If you are in a java environment all the necessary models and commands for an entity can be found here:

• User SDK
• Organization SDK
• Role SDK

implementation("city.smartb.im:user-domain:${Versions.im}")
implementation("city.smartb.im:organization-domain:${Versions.im}")
implementation("city.smartb.im:role-domain:${Versions.im}")

SDK that sugarcoats the http requests are also available:

• User Client
• OrganizationClient
• Role Client

implementation("city.smartb.im:user-client:${Versions.im}")
implementation("city.smartb.im:organization-client:${Versions.im}")
implementation("city.smartb.im:role-client:${Versions.im}")

The client provided in the SDK uses Ktor under the hood and should be a singleton in your application in order to prevent any memory leak. Ex:

@Configuration
class ImConfig(
    private val tokenProvider: TokenProvider
) {

    @Value("\${im.url}")
    lateinit var imUrl: String

    @Bean
    fun userClient() = UserClient(
        url = imUrl,
        generateBearerToken = tokenProvider::getToken
    )

    @Bean
    fun organizationClient() = OrganizationClient(
        url = imUrl,
        generateBearerToken = tokenProvider::getToken
    )

    @Bean
    fun roleClient() = RoleClient(
        url = imUrl,
        generateBearerToken = tokenProvider::getToken
    )
}

Configuration

Properties prefix: i2.issuers[]

Property	Description	Example	Default
uri	Issuer URI accepted by IM	https://auth.smart-b.io/auth/realms/development	http://keycloak-it:8080/realms/test
authUrl	Keycloak server URL	https://auth.smart-b.io/auth	http://keycloak-it:8080
realm	Keycloak realm to authenticate to	development	test
clientId	Client ID used to authenticate with	smartclient	i2-api
clientSecret	Client Secret used to authenticate with	smartsecret	xxxxx

i2.issuers[] should define a list of the above configuration.

For instance:

• In your application.yml file:

i2:
  issuers:
    -
      uri: http://keycloak-it:8080/realms/test
      authUrl: http://keycloak-it:8080
      realm: test
      clientId: i2-api
      clientSecret: clientSecret
    -
      uri: http://keycloak-it:8080/realms/test2
      authUrl: http://keycloak-it:8080
      realm: test2
      clientId: i2-api
      clientSecret: clientSecret2

• By overriding in your docker-compose file:

version: "3.7"
services:
  im-gateway:
    image: smartbcity/im-gateway:${VERSION}
    container_name: im-gateway
    environment:
      server_port: 8004
      i2_issuers[0]_uri: ${ISSUER_URI}
      i2_issuers[0]_authUrl: ${KEYCLOAK_URL}
      i2_issuers[0]_realm: ${KEYCLOAK_REALM}
      i2_issuers[0]_clientId: ${CLIENT_ID}
      i2_issuers[0]_clientSecret: ${CLIENT_SECRET}
      i2_issuers[1]_uri: ${ISSUER_URI_1}
      i2_issuers[1]_authUrl: ${KEYCLOAK_URL_1}
      i2_issuers[1]_realm: ${KEYCLOAK_REALM_1}
      i2_issuers[1]_clientId: ${CLIENT_ID_1}
      i2_issuers[1]_clientSecret: ${CLIENT_SECRET_1}
    ports:
      - "8004:8004"

Properties prefix: i2.organization.insee

Property	Description	Example	Default
token	Token used to authenticate	c6ef3de5-3ef1-330a-8917-21f6750dcb09	c6ef3de5-3ef1-330a-8917-21f6750dcb09
sirene-api	Sirene-api URL	https://api.insee.fr/entreprises/sirene/V3	https://api.insee.fr/entreprises/sirene/V3

Properties prefix: connect.fs

Property	Description	Example	Default
url	Points to an FS instance. This property is optional but will disable associated features if not set (ex: upload logo)	http://localhost:8090	null

Tests

To run tests you need to:

• Start dev environment

make dev up

• Run test

./gradlew test

• Stop dev environment

make dev down

Errors

FileClient not initialized

Message

java.lang.IllegalStateException: FileClient not initialized.

Cause

Appears when trying to use a feature that calls FS but no FS configuration was provided.

Solution

Define a configuration pointing to a valid FS instance or do not use any feature that needs it.

Certificate is not trusted

Message

sun.security.validator.ValidatorException

Cause

The JVM is trying to reach a HTTPS server that is not trusted by the JVM trust store

Solution

Generate a certificate for this server and add it to the trust store

openssl x509 -in <(openssl s_client -connect $HOST:$PORT -prexit 2>/dev/null) -out ~/$ALIAS.crt sudo keytool -importcert -file ~/$ALIAS.crt -alias $ALIAS -keystore $(/usr/libexec/java_home)/lib/security/cacerts -storepass changeit

Database column too small

Cause

We store json in a field designed to just store a string data can be too long

Solution

Execute sql script on keycloak database.

ALTER TABLE public."group_attribute"
ALTER COLUMN value TYPE TEXT;

ALTER TABLE public."user_attribute"
ALTER COLUMN value TYPE TEXT;