Keycloak user/group/role mapping about authcrunch.github.io

[greenpau]

@axi92 , however, you could use “user transforms” to grant roles too. You could match by realm and email to grant someone admin status. Then, match by realm only and grant authp/user.

[greenpau]

If you need I can start the keycloak instance again so you can test on it.

@axi92 good job on exploring the options!!!
I could only work on this on weekends.

[greenpau]

I am wondering whether I missed something in my documentation.

@axi92 , solved it! 👍

[greenpau]

@axi92 , this is where I did not yet figure how to propagate user groups to the id_token sent by Keycloak. I will try finding time to work on it next weekend.

[axi92]

Ok I am on to something, I need some further testing to figure it out how the complete chain works. But I got the default mappings on the client. There are default mappers to do that.

I got now more roles:

  "roles": [
    "create-realm",
    "offline_access",
    "admin",
    "uma_authorization",
    "authp/user"
  ],

[axi92]

I run the caddy in debug mode and decode the id_token on jwt.io there is with the groups also a resource_access.
Can you map that into the User Identity of the authp?

  "resource_access": {
    "caddy-security-portal": {
      "roles": [
        "industria_department-lead",
        "industria_project-lead"
      ]
    }
  },
  "email_verified": false,
  "name": ".....",
  "groups": [
    "create-realm",
    "offline_access",
    "admin",
    "uma_authorization"
  ],

  "resource_access": {
    "<client id>": {
      "roles": [
        "industria_department-lead",
        "industria_project-lead"
      ]
    }
  }

[axi92]

I added 2 built in mappers

If you need I can start the keycloak instance again so you can test on it.

[greenpau]

@axi92 , I just recreated the client setup and ran into the following issue:

2022/05/06 23:05:48.695 WARN    security        Authentication failed   {"session_id": "4Vm8BUcBtIRVLgWMWJIs3ZFfVmQyqVsCIpyAY8mJxkwk6", "request_id": "39579b16-0e37-432e-8cc6-7f15460d166c", "error": "failed validating OAuth 2.0 access token: OAuth 2.0 id_token email claim not found"}

In short the access token sent by Keycloak does not have email field.

Were you able to follow my instructions and get a working portal (although without roles)?

[greenpau]

@axi92 , I am wondering whether I missed something in my documentation.