Automatic generation of unique identities

[michael-ahwoo]

Thank you for your work on this project - it's great!

We are hoping to integrate it into some automated load testing of our OIDC integration that uses Keycloak as a broker and your mock server as an IdP. I've got the whole authorization code flow working, but I'm stuck allowing my JMeter test plan to generate many unique users.

I am using it as a standalone Docker container. This is a fragment of my config.json:

,
    {
      "issuerId": "default2",
      "requestMappings": [
        {
          "requestParam": "grant_type",
          "match": "*",
          "claims": {
            "sub": "${clientId}",
            "email": "my-addressl${clientId}@example.com"
          }
        }
      ]
    }

• The way were are integrated with Keycloak, I can only use a single static value for clientId.
• I can provide unique and arbitrary querystring parameters in the GET to the /authorize endpoint.
• The subsequent POST to the /token endpoint is done by Keycloak and I have little control over what's included.
• Even something simple like allowing a new ${UUID()} token in the config.json to substitute a random string would solve this for me.
• Or, a way to capture a querystring parameter at the /authorize endpoint and reference it in the config.json using the ${parameter} syntax would also solve it.

We are not Kotlin programmers so changing it ourselves is challenging though not impossible.

Thanks!

[tommytroen]

@michael-ahwoo Thanks for submitting this issue, and sorry for the long response time!

Do you need the random value in the email claim also or is it enough with the sub claim? if you leave out the requestmappings entirely you should get sub set to a random uuid (provided you havent set interactiveLogin: true, if thats the case then you will get whatever is put in the login form).