Has Anyone Experienced Issues When Trying to Connect a Keycloak Account in a Pipeline to Get a User?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi everyone, we are trying to connect a Keycloak account in an pipeline to get a user. After countless tries we have been getting the same error message. Has anyone encountered the same problem?

image.png

2

Het , could you share what have you input to the Pipedream Keycloak connection popup?

3

Note that there’s an existing issue here for KeyCloak that the team is checking https://github.com/PipedreamHQ/pipedream/issues/12134. Not sure if it related to yours

4

Hey, We are unfortunately not allowed to share the private key because it is a client project but the client_id: nijiuko url: https://test.idprovider.ksc.de/

5

does this help in any way?

6

The #12134 Issue is not related. Our problem is concerning only the connection to the keycloak account. We did not get further :sweat_smile:

7

, for my case, I follow 3 steps here to make sure my Client got configured properly:

  1. Enable Client Authentication and Service Account Roles (1st image)
  2. On Client Scopes, select the {client_id}-dedicated (2nd image)
  3. Then add the Audience mapping with security-admin-console value

image.png
image.png3360×1926 337 KB

image.png
image.png3360×1926 432 KB

image.png
image.png3360×1926 298 KB

8

@U03CXTHK4RF I believe I saw some connection errors for this app

9

, can you retry without the trailing / at the end of your URL?

10

Danny, I believe it might come from my tests, I faced another issue for this app. I’ve created a ticket here: [BUG] Keycloak - Token inactivated after one operation · Issue #12134 · PipedreamHQ/pipedream · GitHub

11

We made the authentication work but right now we are getting 401-unauthorized, now it seems like the ticket 12134.

12

Thank you for the confirmation.

Kindly subscribe to the ticket to be notified when there’s any updates

13

I commented in the ticket. I would guess the reason for this is the 1 minute validity of the token in Keycloak and it needs to be refreshed.

14

Their access tokens expire after 1 minute?

15

If we go to “Connected Accounts” and reconnect, it works for 1 minute again. Is there a way to reconnect a connected account in a workflow? Otherwise we probably need to create a script that does that for us and keeps the token refreshed