Resurrecting an old question from 2020

[dwickstrom]

We’re trying to use Keycloak as a broker for an ultra common IDP in Sweden, it’s called BankID, and the common implementation involves adding a query parameter to the url that tells the IDP whether to expose a web page with a QR code (which then can be scanned by their mobile application etc), or whether this mobile application resides on the same device. In the latter case you’d get a token and then their application would be opened in the same device.

This look very much like what I’m looking for but it has no effect. This parameter is not forwarded onto the Authorization URL for this idp.

Here’s the old question I was referring to in the topic:

Forwarding the extra query param to the external IdP

I want to forward an extra query param to the external IdP. I have used the option Forwarded Query Parameters in the IdP configuration but it is not putting the query params in the URL. I want to add the launch param to the authorized request. I used by Setting launch to my URL e.g.http://localhost:8080/?launch=abc and set launch in the Forwarded Query Parameters using the URL as the http://localhost:8080 and setting launch=abc in the Forwarded Query Parameters both of these approaches di…

Super thankful for any kind of input!

//David

[dwickstrom]

Okay now, found the solution together with my colleague. So, we learnt that the query params are forwarded from the /auth endpoint, and not from the idp buttons in the keycloak login template.

Nice.