All you need to do is add the plugin to apiman via the API Manager UI
(as an admin). Assuming you are starting from a fresh apiman install.
Once the plugin has been added (no need to download anything separately
- apiman will do that for you) then the OAuth2 policy should be
available when configuring app, service, and plan policies.
-Eric
PS: I know that typing in the GAV information for the plugins is a bit
of a pain - it's on the roadmap to improve this, at least for the
"official" plugins.
On 4/23/2015 12:38 PM, Christina Lau wrote:
Eric, do we need to built the OAuth2 policy ourselves? I just
downloaded it but did not see it included in the UI. Thanks…
Christina
> On Apr 22, 2015, at 1:32 PM, Eric Wittmann <eric.wittmann(a)redhat.com> wrote:
>
> Hey everyone. We released apiman version 1.1.1.Final. There are a few
> news things in this release, but the big reason to do it now was to fix
> a CORS problem that was causing the UI to fail in certain browsers.
> Some users were seeing 403 errors when creating Organizations! Thanks
> to Marc for tracking that down - it was a tough one.
>
> Additionally we have a new policy plugin that turns any JSON REST
> endpoint into a JSONP endpoint:
>
>
https://github.com/apiman/apiman-plugins/tree/master/jsonp-policy
>
> Thanks to Alexandre Kieling for contributing that to us. Much appreciated.
>
> And finally the Keycloak OAuth2 security policy now supports role based
> authorization. When configuring the policy you can now say what roles
> are required for a user to be able to access the service. Thanks to
> Marc for this one as well - good stuff!
>
> -Eric
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/apiman-user