<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">We don't have a mapper for client
attributes. There was no need for it until now AFAIK. You can
either create JIRA to request it (but not sure when it will be
done) or you can implement by yourself. See docs for providers and
SPI [1]<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://keycloak.github.io/docs/userguide/keycloak-server/html/providers.html">http://keycloak.github.io/docs/userguide/keycloak-server/html/providers.html</a><br>
<br>
Marek<br>
<br>
On 14/03/16 11:12, Bram Vonk wrote:<br>
</div>
<blockquote
cite="mid:CANZg7upsRvpasS0z8D=TKkK6rkL7mxVgSLXBpHgKbtADQBimeg@mail.gmail.com"
type="cite">
<div dir="ltr">
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""
lang="EN-US">Hi,</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""
lang="EN-US"><br>
</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""
lang="EN-US">We're adding specific User Attributes to Users,
and
use the User Attribute protocol mapper to add those
attributes to the JWT
bearer tokens the user gets when logging in. <br>
</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""
lang="EN-US"><br>
</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""
lang="EN-US">This works fine for keycloak Users
(natural persons) using our secured endpoints (APIs).</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""
lang="EN-US"><br>
</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""
lang="EN-US">We'd like to use the same concept for Clients
(internal applications, so no natural person is involved)
that use our secured
endpoints. These Clients use client credentials to get a
bearer token from Keycloak. Clients can
have Client Attributes, so that's half the problem fixed.
The other half is the
protocol mapper: there is no Client Attribute protocol
mapper.</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""
lang="EN-US"><br>
</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""
lang="EN-US">Is there a specific reason there is no Client
Attribute protocol mapper? </span><span
style="font-family:"Arial","sans-serif"">Are
we
doing something we shouldn't do? ;)</span></p>
<p class="MsoNormal"><br>
<span
style="font-family:"Arial","sans-serif""></span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">Thanks,</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""><br>
</span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">Bram
Vonk<br>
</span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
keycloak-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-user">https://lists.jboss.org/mailman/listinfo/keycloak-user</a></pre>
</blockquote>
<br>
</body>
</html>