Client Mapper Type: Javascript Mapper

Getting advice
1

Hi All:

2 hopefully quick questions:

  1. Is the Client Protocol Mapper Type ‘Javascript Mapper’ on deprecation path?

  2. Is the Client Protocol Mapper Type ‘Javascript Mapper’ available for both client protocols SAML and OpenID-Connect?

Thank you.

2

I don’t know for sure, but I’m operating on the assumption that javascript mappers are NOT deprecated. in KC18, they deprecated the upload-scripts feature, but made no mention of a long-term plan to deprecate scripts altogether. Here’s the relevant snippet in the release notes: Keycloak 18.0.0 released - Keycloak

For this question, I think it’s probably better to ask on the Keycloak Github Discussions, as the maintainers sometimes answer questions there, but rarely here.

Regarding #2, they work with both types.

1 Like
3

Hi @xgp

FYI - upgraded to v20.0.3 – the JavaScript Mapper for the Client is no longer available. I had read elsewhere that it was deprecated and option is to write code (will like here when I re-find the article).

4

Thanks. Please post when you find the article. Have you included the nashorn jar in your providers dir? I haven’t tested it yet, but I’m assuming you can probably keep this functionality by including the nashorn jar, and maybe the deprecated mapper code.

5

Will do – w.r.t the article.

Meanwhile thje following could be reason why the JavaScript Mapper deprecated:

1 Like
6

@xgp https://github.com/keycloak/keycloak/pull/11322 seems to point that was added to the release – however can’t find any release notes on it or why was removed.

7

@xgp FYI - a kind poster provided the link on the GitHub forum: Server Developer Guide