Hello Eric,<br>my scenario is the following. <br><br>A set of API has been defined to expose core business functions, to clerks and sales force automation. Some functions are specifically sensitive. All access requires end user authentication. Some function are only accessible to users when using trusted clients: for example access from browsers js apps is not enabled to some functions, while native clients for mobile SFA do.<br><br>For trusted application i have implemented OAUTH with signed JWT client authentication (updated KC to latest) almost meeting security requirements (added a ticket to KC for supports of nonces) but oauth client and application are actually unrelated, so no way I can relate the client id to application to enforce access to sensitive api to only users authenticated with the trusted client. <br><br>Of course I can set the api_key header to the one I have associated to the trusted client, but this are unrelated (security department not so happy). I could probably use the api_key as client_id in KC and implement a custom policy to verify the access token audience (i guess that is where the client is mapped in the signed token) matches the apikey.<br><br>In general i was thinking if diffeent strategies for application identification made sense (at api level) .<br><br>Bests<br>Mike<br><br><div class="gmail_quote"><div dir="ltr">On Thu, 14 Jan 2016 at 14:34, Eric Wittmann <<a href="mailto:eric.wittmann@redhat.com">eric.wittmann@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Michele.<br>
<br>
That is correct. Typically the end-user population is tied to the API<br>
being invoked rather than the Client (software) being used to connect.<br>
If that is not the case, then you could configure the OAuth policy on<br>
the Client Application rather than on the API (Service). That way you<br>
could have a different user population for each connecting client. If<br>
that's your use-case I'd love to hear more about it. :)<br>
<br>
-Eric<br>
<br>
On 1/13/2016 3:05 PM, michele danieli wrote:<br>
> When considering non public API and applying a OAuth authentication<br>
> policy, the application identifier must be provided using the api_key as<br>
> a header?<br>
><br>
> If so, does not it means that the user authorized client and the actual<br>
> api consumer application have no strict relationship?<br>
><br>
><br>
> Thanks<br>
> Michele<br>
><br>
><br>
> _______________________________________________<br>
> Apiman-user mailing list<br>
> <a href="mailto:Apiman-user@lists.jboss.org" target="_blank">Apiman-user@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/apiman-user</a><br>
><br>
</blockquote></div>