Re: [Apiman-user] Getting Started (Docker): Invalid redirect_uri
by Dennis Kieselhorst
Hi Marc!
> This has now been fixed, thanks for letting me know, Dennis.
>
> On 13/04/2015 11:18, Marc Savy wrote:
>> With regards to your inability to find /apimanui/, it looks like a
>> mistake has been made and the dockerhub image hasn't been uploaded for
>> the latest release (i.e. it's still the 1.0.3 release, and hence the
>> manager will be on the old address of /apiman-manager/). I'll do what I
>> can to get this fixed ASAP; many thanks for letting us know!
>>
It's working now, thanks!
Regards
Dennis
10 years, 11 months
News: apiman 1.1.1.Final released!
by Eric Wittmann
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
10 years, 11 months
Testing feedback: apiman Oauth2 with Keycloak roles authentication
by Marc Savy
Hi All,
I've had a few questions about doing authorization against Keycloak
roles. For any brave testers out there, I'm interested to get feedback
on an initial implementation of that:
How to:
- Build master of http://github.com/apiman/apiman-plugins locally (`mvn
clean install`)
- Install the plugin via the UI (or API):
G io.apiman.plugins
A apiman-plugins-keycloak-oauth-policy
V 1.1.1-SNAPSHOT
- Set everything up in Keycloak. For instance, I added an application
mapping role, apiman-service => apiman-gateway-user-role and a realm
role `apiman-realm-role-example`.
- Set up the Keycloak Oauth policy, including the realm and application
mappings you're interested in.
- You might want to disable "Require Transport Security" to make your
testing easier.
I'm interested to hear feedback - does this fulfil your requirements,
are there any additional features that are required?
Regards,
Marc
10 years, 12 months
403 Error when creating an organization
by Alexandre Kieling
Hi all,
I'm getting a 403 error when trying to create an organization.
I'm using the 'admin' user and the latest code from master.
Could someone please have a look?
Alexandre Kieling
11 years
New Release: 1.1.0.Final
by Eric Wittmann
Hello everyone!
Today we released apiman version 1.1.0.Final. There are many new
features/changes in this release, including but not limited to:
* Support for Elasticsearch as the storage provider for the API Manager
* Support for Elasticsearch for various API Gateway components
* New Keycloak based OAuth2 authentication policy
* The UI is now written entirely in angularjs instead of GWT
That last bullet point took a lot of work, which is why there was such a
delay between our last 1.0.x release and this first 1.1.0.Final release.
Now that the UI work is done, we can get back to the business of
frequently releasing new incremental features!
-Eric
11 years
