thomasdarimont

Hallo zusammen,

ich habe mich heute abend mal hingesetzt und euren Branch ... auf den aktuellen Keycloak master rebased und zur Integration einen neuen Branch erstellt: Danach habe ich die commits aus meinem validation-spi branch in einen commit gesquashed und cherry-picked.

Der branch kompiliert nun und kann nun als Grundlage für einen experimentiellen Umbau dienen. Ich denke wir sollten uns dazu nochmal abstimmen und ggf. ne Pairing Session machen.

Ich denke mittlerweile, dass man über 80% euerer klassen mit dem generischen Validation SPI ersetzen kann.

thomasdarimont

package demo.userstorage.demouserstorage;

import lombok.extern.jbosslog.JBossLog;
import org.jboss.resteasy.spi.HttpRequest;
import org.jboss.resteasy.spi.ResteasyProviderFactory;
import org.keycloak.authentication.AuthenticationFlowError;
import org.keycloak.authentication.AuthenticationFlowException;
import org.keycloak.component.ComponentModel;
import org.keycloak.credential.CredentialInput;
import org.keycloak.credential.CredentialInputUpdater;

thomasdarimont

package demo;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.boot.autoconfigure.liquibase.LiquibaseAutoConfiguration;

@SpringBootApplication(exclude = LiquibaseAutoConfiguration.class)
public class Main {

    public static void main(String[] args) {

thomasdarimont

package com.github.thomasdarimont.keycloak.auth.dynamicidp;

import lombok.extern.jbosslog.JBossLog;
import org.keycloak.OAuth2Constants;
import org.keycloak.authentication.AuthenticationFlowContext;
import org.keycloak.authentication.AuthenticationFlowError;
import org.keycloak.authentication.Authenticator;
import org.keycloak.constants.AdapterConstants;
import org.keycloak.events.Errors;
import org.keycloak.models.AuthenticatorConfigModel;

thomasdarimont

use core::fmt;
use std::io::{self, Write};

#[derive(Debug, Clone, Copy)]
enum BinaryOperator {
    ADD,
    SUB,
    MUL,
    DIV,
    MOD,

thomasdarimont

See https://apex.oracle.com/pls/apex/germancommunities/dbacommunity/tipp/6241/index.html

Create database

docker run -d -it -p 1521:1521 --name oracle-db store/oracle/database-enterprise:12.2.0.1-slim

Create user

thomasdarimont

JAVA_TARGET=$PWD/java-runtime

echo "Create trimmed down JDK" && \
      $JAVA_HOME/bin/jlink \
      --no-header-files \
      --no-man-pages \
      --compress=2 \
      --vm=server \
      --exclude-files="**/bin/rmiregistry,**/bin/jrunscript,**/bin/rmid" \

thomasdarimont

import org.keycloak.models.ProtocolMapperModel;
import org.keycloak.models.UserModel;
import org.keycloak.models.UserSessionModel;
import org.keycloak.protocol.ProtocolMapperUtils;
import org.keycloak.protocol.oidc.mappers.OIDCAttributeMapperHelper;
import org.keycloak.protocol.oidc.mappers.UserAttributeMapper;
import org.keycloak.representations.IDToken;

import java.util.Collection;
import java.util.HashSet;

thomasdarimont

How enable Micro Profile OpenTracing in Keycloak 10.x

Keycloak 10.0.1 is based on Wildfly 19 which comes with support for OpenTracing. However the OpenTracing support in Keycloak is not active by default. This small example demonstrates how to enable OpenTracing in the latest Keycloak version based on the article Micro_Profile_OpenTracing_Comes_To_WildFly

This example tries to explore a solution for KEYCLOAK-8288.

thomasdarimont

Create and mount RAM disk

mkdir -p /tmp/build
sudo mount -t tmpfs -o size=512M tmpfs /tmp/build

Unmount RAM disk

sudo umount /tmp/build