9:44 a.m.
I have a problem in calling a service in apiman-gateway with the
Authorization: Bearer <token> in the header.
It seems to preflight OPTIONS and return
1. X-Policy-Failure-Message:
OAuth2 'Authorization' header or 'access_token' query parameter must
be
provided.
I am sending the bearer token with the request and i make sure in the
preflight its sent in the request.
1. Access-Control-Request-Headers:
accept, authorization
Does anyone know if there Is something i'm missing ? do i need to get
authorization enabled or added anywhere ? as a side note i have below in my
api as well:
response.setHeader("Access-Control-Allow-Headers", "Authorization");
9:52 a.m.
Hi,
This is related to the JIRA I linked you to (https://issues.jboss.org/browse/APIMAN-516).
Because of the way the policy chain currently works the behaviour of CORS is invalid in a
few very specific cases (e.g. when you stack it with an auth policy). I'll let you
know when it's fixed.
Regards,
Marc
On 17/08/2015 15:44, Fadi Abdin wrote:
I have a problem in calling a service in apiman-gateway with the
Authorization: Bearer <token> in the header.
It seems to preflight OPTIONS and return
1.
X-Policy-Failure-Message:
OAuth2 'Authorization' header or 'access_token' query parameter must
be provided.
I am sending the bearer token with the request and i make sure in the
preflight its sent in the request.
1.
Access-Control-Request-Headers:
accept, authorization
Does anyone know if there Is something i'm missing ? do i need to get
authorization enabled or added anywhere ? as a side note i have below in
my api as well:
response.setHeader("Access-Control-Allow-Headers", "Authorization");
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user
10:23 a.m.
Thank you Marc,
Is there a work around that you can think of ?
I'm doing it with angularjs , very simple
$http({method: 'GET', url: 'http://server/apiman-gateway/service',
headers:
{
'Authorization': 'Bearer XXXXXXXXXXXXX'}
});
I assume you will fix it in the new version , right?
On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy <marc.savy(a)redhat.com> wrote:
Hi,
This is related to the JIRA I linked you to (
https://issues.jboss.org/browse/APIMAN-516). Because of the way the
policy chain currently works the behaviour of CORS is invalid in a few very
specific cases (e.g. when you stack it with an auth policy). I'll let you
know when it's fixed.
Regards,
Marc
On 17/08/2015 15:44, Fadi Abdin wrote:
> I have a problem in calling a service in apiman-gateway with the
> Authorization: Bearer <token> in the header.
>
> It seems to preflight OPTIONS and return
>
> 1.
> X-Policy-Failure-Message:
> OAuth2 'Authorization' header or 'access_token' query parameter
must
> be provided.
>
> I am sending the bearer token with the request and i make sure in the
> preflight its sent in the request.
>
> 1.
> Access-Control-Request-Headers:
> accept, authorization
>
> Does anyone know if there Is something i'm missing ? do i need to get
> authorization enabled or added anywhere ? as a side note i have below in
> my api as well:
>
> response.setHeader("Access-Control-Allow-Headers",
"Authorization");
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
10:37 a.m.
I'm actually testing the fix right now. It will land both on the 1.2.x
branch and the 1.1.x branch shortly. You should be able to test it out
in a short while: I'll send you an email when it's available.
On 17/08/2015 16:23, Fadi Abdin wrote:
Thank you Marc,
Is there a work around that you can think of ?
I'm doing it with angularjs , very simple
$http({method: 'GET', url: 'http://server/apiman-gateway/service',
headers: {
'Authorization': 'Bearer XXXXXXXXXXXXX'}
});
I assume you will fix it in the new version , right?
On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy <marc.savy(a)redhat.com
<mailto:marc.savy@redhat.com>> wrote:
Hi,
This is related to the JIRA I linked you to
(https://issues.jboss.org/browse/APIMAN-516). Because of the way the
policy chain currently works the behaviour of CORS is invalid in a
few very specific cases (e.g. when you stack it with an auth
policy). I'll let you know when it's fixed.
Regards,
Marc
On 17/08/2015 15:44, Fadi Abdin wrote:
I have a problem in calling a service in apiman-gateway with the
Authorization: Bearer <token> in the header.
It seems to preflight OPTIONS and return
1.
X-Policy-Failure-Message:
OAuth2 'Authorization' header or 'access_token' query
parameter must
be provided.
I am sending the bearer token with the request and i make sure
in the
preflight its sent in the request.
1.
Access-Control-Request-Headers:
accept, authorization
Does anyone know if there Is something i'm missing ? do i need
to get
authorization enabled or added anywhere ? as a side note i have
below in
my api as well:
response.setHeader("Access-Control-Allow-Headers",
"Authorization");
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
10:38 a.m.
cool .. you're the man ;)
On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy <marc.savy(a)redhat.com> wrote:
I'm actually testing the fix right now. It will land both on the
1.2.x
branch and the 1.1.x branch shortly. You should be able to test it out
in a short while: I'll send you an email when it's available.
On 17/08/2015 16:23, Fadi Abdin wrote:
> Thank you Marc,
> Is there a work around that you can think of ?
> I'm doing it with angularjs , very simple
>
> $http({method: 'GET', url: 'http://server/apiman-gateway/service',
> headers: {
> 'Authorization': 'Bearer XXXXXXXXXXXXX'}
> });
>
> I assume you will fix it in the new version , right?
>
>
>
> On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy <marc.savy(a)redhat.com
> <mailto:marc.savy@redhat.com>> wrote:
>
> Hi,
>
> This is related to the JIRA I linked you to
> (https://issues.jboss.org/browse/APIMAN-516). Because of the way the
> policy chain currently works the behaviour of CORS is invalid in a
> few very specific cases (e.g. when you stack it with an auth
> policy). I'll let you know when it's fixed.
>
> Regards,
> Marc
>
> On 17/08/2015 15:44, Fadi Abdin wrote:
>
> I have a problem in calling a service in apiman-gateway with the
> Authorization: Bearer <token> in the header.
>
> It seems to preflight OPTIONS and return
>
> 1.
> X-Policy-Failure-Message:
> OAuth2 'Authorization' header or 'access_token' query
> parameter must
> be provided.
>
> I am sending the bearer token with the request and i make sure
> in the
> preflight its sent in the request.
>
> 1.
> Access-Control-Request-Headers:
> accept, authorization
>
> Does anyone know if there Is something i'm missing ? do i need
> to get
> authorization enabled or added anywhere ? as a side note i have
> below in
> my api as well:
>
> response.setHeader("Access-Control-Allow-Headers",
> "Authorization");
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
>
>
11:24 a.m.
+1
On 8/17/2015 11:38 AM, Fadi Abdin wrote:
cool .. you're the man ;)
On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy <marc.savy(a)redhat.com
<mailto:marc.savy@redhat.com>> wrote:
I'm actually testing the fix right now. It will land both on the 1.2.x
branch and the 1.1.x branch shortly. You should be able to test it out
in a short while: I'll send you an email when it's available.
On 17/08/2015 16:23, Fadi Abdin wrote:
Thank you Marc,
Is there a work around that you can think of ?
I'm doing it with angularjs , very simple
$http({method: 'GET', url:
'http://server/apiman-gateway/service',
headers: {
'Authorization': 'Bearer XXXXXXXXXXXXX'}
});
I assume you will fix it in the new version , right?
On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
<marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>>
wrote:
Hi,
This is related to the JIRA I linked you to
(https://issues.jboss.org/browse/APIMAN-516). Because of
the way the
policy chain currently works the behaviour of CORS is
invalid in a
few very specific cases (e.g. when you stack it with an auth
policy). I'll let you know when it's fixed.
Regards,
Marc
On 17/08/2015 15:44, Fadi Abdin wrote:
I have a problem in calling a service in apiman-gateway
with the
Authorization: Bearer <token> in the header.
It seems to preflight OPTIONS and return
1.
X-Policy-Failure-Message:
OAuth2 'Authorization' header or 'access_token'
query
parameter must
be provided.
I am sending the bearer token with the request and i
make sure
in the
preflight its sent in the request.
1.
Access-Control-Request-Headers:
accept, authorization
Does anyone know if there Is something i'm missing ?
do i need
to get
authorization enabled or added anywhere ? as a side
note i have
below in
my api as well:
response.setHeader("Access-Control-Allow-Headers",
"Authorization");
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>
https://lists.jboss.org/mailman/listinfo/apiman-user
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user
12:32 p.m.
Hi Fadi,
Please feel free to try this out - you'll be building 1.1.7-SNAPSHOT
of apiman/apiman and apiman/apiman-plugins.
apiman:
git fetch origin pull/180/head:fix-cors
git checkout fix-cors
mvn clean install
apiman-plugins:
git fetch origin pull/26/head:fix-cors
git checkout fix-cors
mvn clean install
Make sure you build them in the order shown above and use 1.1.7-SNAPSHOT
of the CORS plugin.
This is using a snapshot from my PRs, so please don't forget about it
later, otherwise you'll be stuck on an old version!
Regards,
Marc
On 17/08/2015 16:38, Fadi Abdin wrote:
cool .. you're the man ;)
On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy <marc.savy(a)redhat.com
<mailto:marc.savy@redhat.com>> wrote:
I'm actually testing the fix right now. It will land both on the 1.2.x
branch and the 1.1.x branch shortly. You should be able to test it out
in a short while: I'll send you an email when it's available.
On 17/08/2015 16:23, Fadi Abdin wrote:
Thank you Marc,
Is there a work around that you can think of ?
I'm doing it with angularjs , very simple
$http({method: 'GET', url:
'http://server/apiman-gateway/service',
headers: {
'Authorization': 'Bearer XXXXXXXXXXXXX'}
});
I assume you will fix it in the new version , right?
On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
<marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>>
wrote:
Hi,
This is related to the JIRA I linked you to
(https://issues.jboss.org/browse/APIMAN-516). Because of
the way the
policy chain currently works the behaviour of CORS is
invalid in a
few very specific cases (e.g. when you stack it with an auth
policy). I'll let you know when it's fixed.
Regards,
Marc
On 17/08/2015 15:44, Fadi Abdin wrote:
I have a problem in calling a service in apiman-gateway
with the
Authorization: Bearer <token> in the header.
It seems to preflight OPTIONS and return
1.
X-Policy-Failure-Message:
OAuth2 'Authorization' header or 'access_token'
query
parameter must
be provided.
I am sending the bearer token with the request and i
make sure
in the
preflight its sent in the request.
1.
Access-Control-Request-Headers:
accept, authorization
Does anyone know if there Is something i'm missing ?
do i need
to get
authorization enabled or added anywhere ? as a side
note i have
below in
my api as well:
response.setHeader("Access-Control-Allow-Headers",
"Authorization");
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>
https://lists.jboss.org/mailman/listinfo/apiman-user
1:02 p.m.
Or if you can wait for 30 minutes you can do all this from 'master' or
from the '1.1.x' branch. :)
-Eric
On 8/17/2015 1:32 PM, Marc Savy wrote:
Hi Fadi,
Please feel free to try this out - you'll be building 1.1.7-SNAPSHOT
of apiman/apiman and apiman/apiman-plugins.
apiman:
git fetch origin pull/180/head:fix-cors
git checkout fix-cors
mvn clean install
apiman-plugins:
git fetch origin pull/26/head:fix-cors
git checkout fix-cors
mvn clean install
Make sure you build them in the order shown above and use 1.1.7-SNAPSHOT
of the CORS plugin.
This is using a snapshot from my PRs, so please don't forget about it
later, otherwise you'll be stuck on an old version!
Regards,
Marc
On 17/08/2015 16:38, Fadi Abdin wrote:
> cool .. you're the man ;)
>
>
> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy <marc.savy(a)redhat.com
> <mailto:marc.savy@redhat.com>> wrote:
>
> I'm actually testing the fix right now. It will land both on the 1.2.x
> branch and the 1.1.x branch shortly. You should be able to test it out
> in a short while: I'll send you an email when it's available.
>
> On 17/08/2015 16:23, Fadi Abdin wrote:
>
> Thank you Marc,
> Is there a work around that you can think of ?
> I'm doing it with angularjs , very simple
>
> $http({method: 'GET', url:
'http://server/apiman-gateway/service',
> headers: {
> 'Authorization': 'Bearer XXXXXXXXXXXXX'}
> });
>
> I assume you will fix it in the new version , right?
>
>
>
> On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
> <mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>>
wrote:
>
> Hi,
>
> This is related to the JIRA I linked you to
> (https://issues.jboss.org/browse/APIMAN-516). Because of
> the way the
> policy chain currently works the behaviour of CORS is
> invalid in a
> few very specific cases (e.g. when you stack it with an auth
> policy). I'll let you know when it's fixed.
>
> Regards,
> Marc
>
> On 17/08/2015 15:44, Fadi Abdin wrote:
>
> I have a problem in calling a service in apiman-gateway
> with the
> Authorization: Bearer <token> in the header.
>
> It seems to preflight OPTIONS and return
>
> 1.
> X-Policy-Failure-Message:
> OAuth2 'Authorization' header or
'access_token' query
> parameter must
> be provided.
>
> I am sending the bearer token with the request and i
> make sure
> in the
> preflight its sent in the request.
>
> 1.
> Access-Control-Request-Headers:
> accept, authorization
>
> Does anyone know if there Is something i'm missing ?
> do i need
> to get
> authorization enabled or added anywhere ? as a side
> note i have
> below in
> my api as well:
>
> response.setHeader("Access-Control-Allow-Headers",
> "Authorization");
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
>
>
>
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user
1:11 p.m.
yeah i can wait.
The way i run apiman is by downloading wildfly and the apiman-overlay zip
files and then unzip and run ..
Do you have instructions somewhere to update with a new version by building
the code ? i can mvn install and drop the files , but i dont think this is
enough , is it ?
On Mon, Aug 17, 2015 at 2:02 PM, Eric Wittmann <eric.wittmann(a)redhat.com>
wrote:
Or if you can wait for 30 minutes you can do all this from
'master' or
from the '1.1.x' branch. :)
-Eric
On 8/17/2015 1:32 PM, Marc Savy wrote:
> Hi Fadi,
>
> Please feel free to try this out - you'll be building 1.1.7-SNAPSHOT
> of apiman/apiman and apiman/apiman-plugins.
>
> apiman:
>
> git fetch origin pull/180/head:fix-cors
> git checkout fix-cors
> mvn clean install
>
> apiman-plugins:
>
> git fetch origin pull/26/head:fix-cors
> git checkout fix-cors
> mvn clean install
>
> Make sure you build them in the order shown above and use 1.1.7-SNAPSHOT
> of the CORS plugin.
>
> This is using a snapshot from my PRs, so please don't forget about it
> later, otherwise you'll be stuck on an old version!
>
> Regards,
> Marc
>
> On 17/08/2015 16:38, Fadi Abdin wrote:
>
>> cool .. you're the man ;)
>>
>>
>> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy <marc.savy(a)redhat.com
>> <mailto:marc.savy@redhat.com>> wrote:
>>
>> I'm actually testing the fix right now. It will land both on the
>> 1.2.x
>> branch and the 1.1.x branch shortly. You should be able to test it
>> out
>> in a short while: I'll send you an email when it's available.
>>
>> On 17/08/2015 16:23, Fadi Abdin wrote:
>>
>> Thank you Marc,
>> Is there a work around that you can think of ?
>> I'm doing it with angularjs , very simple
>>
>> $http({method: 'GET', url: '
>> http://server/apiman-gateway/service';,
>> headers: {
>> 'Authorization': 'Bearer XXXXXXXXXXXXX'}
>> });
>>
>> I assume you will fix it in the new version , right?
>>
>>
>>
>> On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
>> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
>> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>>
>> wrote:
>>
>> Hi,
>>
>> This is related to the JIRA I linked you to
>> (https://issues.jboss.org/browse/APIMAN-516). Because of
>> the way the
>> policy chain currently works the behaviour of CORS is
>> invalid in a
>> few very specific cases (e.g. when you stack it with an
>> auth
>> policy). I'll let you know when it's fixed.
>>
>> Regards,
>> Marc
>>
>> On 17/08/2015 15:44, Fadi Abdin wrote:
>>
>> I have a problem in calling a service in apiman-gateway
>> with the
>> Authorization: Bearer <token> in the header.
>>
>> It seems to preflight OPTIONS and return
>>
>> 1.
>> X-Policy-Failure-Message:
>> OAuth2 'Authorization' header or
'access_token'
>> query
>> parameter must
>> be provided.
>>
>> I am sending the bearer token with the request and i
>> make sure
>> in the
>> preflight its sent in the request.
>>
>> 1.
>> Access-Control-Request-Headers:
>> accept, authorization
>>
>> Does anyone know if there Is something i'm missing ?
>> do i need
>> to get
>> authorization enabled or added anywhere ? as a side
>> note i have
>> below in
>> my api as well:
>>
>> response.setHeader("Access-Control-Allow-Headers",
>> "Authorization");
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org
>> >
>> <mailto:Apiman-user@lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>>
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>
>>
>>
>>
>>
>>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
1:47 p.m.
If you build apiman from source using maven, the same ZIP file you've
been using via the download mechanism will be created. For example:
git clone git@github.com:apiman/apiman.git
cd apiman
git checkout 1.1.x
mvn clean install -DskipTests
ls -al
distro/wildfly8/target/apiman-distro-wildfly8-1.2.0-SNAPSHOT-overlay.zip
That file should now exist - you can copy it off somewhere and use it
just like the one you normally download.
For the plugin, you simply need to check out the code and build it.
Then you can add the plugin via the UI as normal. Example:
git clone git@github.com:apiman/apiman-plugins.git
cd apiman-plugins
mvn clean install
Then use the UI to install it.
-Eric
On 8/17/2015 2:11 PM, Fadi Abdin wrote:
yeah i can wait.
The way i run apiman is by downloading wildfly and the apiman-overlay
zip files and then unzip and run ..
Do you have instructions somewhere to update with a new version by
building the code ? i can mvn install and drop the files , but i dont
think this is enough , is it ?
On Mon, Aug 17, 2015 at 2:02 PM, Eric Wittmann <eric.wittmann(a)redhat.com
<mailto:eric.wittmann@redhat.com>> wrote:
Or if you can wait for 30 minutes you can do all this from 'master'
or from the '1.1.x' branch. :)
-Eric
On 8/17/2015 1:32 PM, Marc Savy wrote:
Hi Fadi,
Please feel free to try this out - you'll be building 1.1.7-SNAPSHOT
of apiman/apiman and apiman/apiman-plugins.
apiman:
git fetch origin pull/180/head:fix-cors
git checkout fix-cors
mvn clean install
apiman-plugins:
git fetch origin pull/26/head:fix-cors
git checkout fix-cors
mvn clean install
Make sure you build them in the order shown above and use
1.1.7-SNAPSHOT
of the CORS plugin.
This is using a snapshot from my PRs, so please don't forget
about it
later, otherwise you'll be stuck on an old version!
Regards,
Marc
On 17/08/2015 16:38, Fadi Abdin wrote:
cool .. you're the man ;)
On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy
<marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>>
wrote:
I'm actually testing the fix right now. It will land
both on the 1.2.x
branch and the 1.1.x branch shortly. You should be
able to test it out
in a short while: I'll send you an email when it's
available.
On 17/08/2015 16:23, Fadi Abdin wrote:
Thank you Marc,
Is there a work around that you can think of ?
I'm doing it with angularjs , very simple
$http({method: 'GET', url:
'http://server/apiman-gateway/service',
headers: {
'Authorization': 'Bearer XXXXXXXXXXXXX'}
});
I assume you will fix it in the new version , right?
On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
<marc.savy(a)redhat.com
<mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>
<mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>>> wrote:
Hi,
This is related to the JIRA I linked you to
(https://issues.jboss.org/browse/APIMAN-516).
Because of
the way the
policy chain currently works the behaviour of
CORS is
invalid in a
few very specific cases (e.g. when you stack
it with an auth
policy). I'll let you know when it's fixed.
Regards,
Marc
On 17/08/2015 15:44, Fadi Abdin wrote:
I have a problem in calling a service in
apiman-gateway
with the
Authorization: Bearer <token> in the header.
It seems to preflight OPTIONS and return
1.
X-Policy-Failure-Message:
OAuth2 'Authorization' header or
'access_token' query
parameter must
be provided.
I am sending the bearer token with the
request and i
make sure
in the
preflight its sent in the request.
1.
Access-Control-Request-Headers:
accept, authorization
Does anyone know if there Is something
i'm missing ?
do i need
to get
authorization enabled or added anywhere ?
as a side
note i have
below in
my api as well:
response.setHeader("Access-Control-Allow-Headers",
"Authorization");
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>>
https://lists.jboss.org/mailman/listinfo/apiman-user
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
1:56 p.m.
Correction on my instructions below. Thanks to msavy for pointing this out:
git clone git@github.com:apiman/apiman.git
cd apiman
git checkout 1.1.x
mvn clean install -DskipTests
ls -al
distro/wildfly8/target/apiman-distro-wildfly8-1.1.7-SNAPSHOT-overlay.zip
Also don't forget to use 1.1.7-SNAPSHOT when you install the CORS plugin.
-Eric
On 8/17/2015 2:47 PM, Eric Wittmann wrote:
If you build apiman from source using maven, the same ZIP file
you've
been using via the download mechanism will be created. For example:
git clone git@github.com:apiman/apiman.git
cd apiman
git checkout 1.1.x
mvn clean install -DskipTests
ls -al
distro/wildfly8/target/apiman-distro-wildfly8-1.2.0-SNAPSHOT-overlay.zip
That file should now exist - you can copy it off somewhere and use it
just like the one you normally download.
For the plugin, you simply need to check out the code and build it. Then
you can add the plugin via the UI as normal. Example:
git clone git@github.com:apiman/apiman-plugins.git
cd apiman-plugins
mvn clean install
Then use the UI to install it.
-Eric
On 8/17/2015 2:11 PM, Fadi Abdin wrote:
> yeah i can wait.
>
> The way i run apiman is by downloading wildfly and the apiman-overlay
> zip files and then unzip and run ..
>
> Do you have instructions somewhere to update with a new version by
> building the code ? i can mvn install and drop the files , but i dont
> think this is enough , is it ?
>
> On Mon, Aug 17, 2015 at 2:02 PM, Eric Wittmann <eric.wittmann(a)redhat.com
> <mailto:eric.wittmann@redhat.com>> wrote:
>
> Or if you can wait for 30 minutes you can do all this from 'master'
> or from the '1.1.x' branch. :)
>
> -Eric
>
>
> On 8/17/2015 1:32 PM, Marc Savy wrote:
>
> Hi Fadi,
>
> Please feel free to try this out - you'll be building
> 1.1.7-SNAPSHOT
> of apiman/apiman and apiman/apiman-plugins.
>
> apiman:
>
> git fetch origin pull/180/head:fix-cors
> git checkout fix-cors
> mvn clean install
>
> apiman-plugins:
>
> git fetch origin pull/26/head:fix-cors
> git checkout fix-cors
> mvn clean install
>
> Make sure you build them in the order shown above and use
> 1.1.7-SNAPSHOT
> of the CORS plugin.
>
> This is using a snapshot from my PRs, so please don't forget
> about it
> later, otherwise you'll be stuck on an old version!
>
> Regards,
> Marc
>
> On 17/08/2015 16:38, Fadi Abdin wrote:
>
> cool .. you're the man ;)
>
>
> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy
> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>>
> wrote:
>
> I'm actually testing the fix right now. It will land
> both on the 1.2.x
> branch and the 1.1.x branch shortly. You should be
> able to test it out
> in a short while: I'll send you an email when it's
> available.
>
> On 17/08/2015 16:23, Fadi Abdin wrote:
>
> Thank you Marc,
> Is there a work around that you can think of ?
> I'm doing it with angularjs , very simple
>
> $http({method: 'GET', url:
> 'http://server/apiman-gateway/service',
> headers: {
> 'Authorization': 'Bearer XXXXXXXXXXXXX'}
> });
>
> I assume you will fix it in the new version ,
> right?
>
>
>
> On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
> <marc.savy(a)redhat.com
> <mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>>
> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>>>> wrote:
>
> Hi,
>
> This is related to the JIRA I linked you to
> (https://issues.jboss.org/browse/APIMAN-516).
> Because of
> the way the
> policy chain currently works the behaviour of
> CORS is
> invalid in a
> few very specific cases (e.g. when you stack
> it with an auth
> policy). I'll let you know when it's fixed.
>
> Regards,
> Marc
>
> On 17/08/2015 15:44, Fadi Abdin wrote:
>
> I have a problem in calling a service in
> apiman-gateway
> with the
> Authorization: Bearer <token> in the
> header.
>
> It seems to preflight OPTIONS and return
>
> 1.
> X-Policy-Failure-Message:
> OAuth2 'Authorization' header or
> 'access_token' query
> parameter must
> be provided.
>
> I am sending the bearer token with the
> request and i
> make sure
> in the
> preflight its sent in the request.
>
> 1.
> Access-Control-Request-Headers:
> accept, authorization
>
> Does anyone know if there Is something
> i'm missing ?
> do i need
> to get
> authorization enabled or added anywhere ?
> as a side
> note i have
> below in
> my api as well:
>
>
> response.setHeader("Access-Control-Allow-Headers",
> "Authorization");
>
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>>
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
>
>
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
8:46 a.m.
My pleasure! Did it work?
On 17/08/2015 16:38, Fadi Abdin wrote:
cool .. you're the man ;)
On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy <marc.savy(a)redhat.com
<mailto:marc.savy@redhat.com>> wrote:
I'm actually testing the fix right now. It will land both on the 1.2.x
branch and the 1.1.x branch shortly. You should be able to test it out
in a short while: I'll send you an email when it's available.
On 17/08/2015 16:23, Fadi Abdin wrote:
Thank you Marc,
Is there a work around that you can think of ?
I'm doing it with angularjs , very simple
$http({method: 'GET', url:
'http://server/apiman-gateway/service',
headers: {
'Authorization': 'Bearer XXXXXXXXXXXXX'}
});
I assume you will fix it in the new version , right?
On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
<marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>>
wrote:
Hi,
This is related to the JIRA I linked you to
(https://issues.jboss.org/browse/APIMAN-516). Because of
the way the
policy chain currently works the behaviour of CORS is
invalid in a
few very specific cases (e.g. when you stack it with an auth
policy). I'll let you know when it's fixed.
Regards,
Marc
On 17/08/2015 15:44, Fadi Abdin wrote:
I have a problem in calling a service in apiman-gateway
with the
Authorization: Bearer <token> in the header.
It seems to preflight OPTIONS and return
1.
X-Policy-Failure-Message:
OAuth2 'Authorization' header or 'access_token'
query
parameter must
be provided.
I am sending the bearer token with the request and i
make sure
in the
preflight its sent in the request.
1.
Access-Control-Request-Headers:
accept, authorization
Does anyone know if there Is something i'm missing ?
do i need
to get
authorization enabled or added anywhere ? as a side
note i have
below in
my api as well:
response.setHeader("Access-Control-Allow-Headers",
"Authorization");
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>
https://lists.jboss.org/mailman/listinfo/apiman-user
9:48 a.m.
I'm still working on it :( .. i had to give the network guys few ip
addresses to whitelist so i can mvn install .. ... almost there.
On Tue, Aug 18, 2015 at 9:46 AM, Marc Savy <marc.savy(a)redhat.com> wrote:
My pleasure! Did it work?
On 17/08/2015 16:38, Fadi Abdin wrote:
> cool .. you're the man ;)
>
>
> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy <marc.savy(a)redhat.com
> <mailto:marc.savy@redhat.com>> wrote:
>
> I'm actually testing the fix right now. It will land both on the 1.2.x
> branch and the 1.1.x branch shortly. You should be able to test it out
> in a short while: I'll send you an email when it's available.
>
> On 17/08/2015 16:23, Fadi Abdin wrote:
>
> Thank you Marc,
> Is there a work around that you can think of ?
> I'm doing it with angularjs , very simple
>
> $http({method: 'GET', url: 'http://server/apiman-gateway/service
> ',
> headers: {
> 'Authorization': 'Bearer XXXXXXXXXXXXX'}
> });
>
> I assume you will fix it in the new version , right?
>
>
>
> On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
> <mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>>
> wrote:
>
> Hi,
>
> This is related to the JIRA I linked you to
> (https://issues.jboss.org/browse/APIMAN-516). Because of
> the way the
> policy chain currently works the behaviour of CORS is
> invalid in a
> few very specific cases (e.g. when you stack it with an auth
> policy). I'll let you know when it's fixed.
>
> Regards,
> Marc
>
> On 17/08/2015 15:44, Fadi Abdin wrote:
>
> I have a problem in calling a service in apiman-gateway
> with the
> Authorization: Bearer <token> in the header.
>
> It seems to preflight OPTIONS and return
>
> 1.
> X-Policy-Failure-Message:
> OAuth2 'Authorization' header or
'access_token'
> query
> parameter must
> be provided.
>
> I am sending the bearer token with the request and i
> make sure
> in the
> preflight its sent in the request.
>
> 1.
> Access-Control-Request-Headers:
> accept, authorization
>
> Does anyone know if there Is something i'm missing ?
> do i need
> to get
> authorization enabled or added anywhere ? as a side
> note i have
> below in
> my api as well:
>
> response.setHeader("Access-Control-Allow-Headers",
> "Authorization");
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
>
>
>
>
1:25 p.m.
It did not work .
I setup everything they way you told me Marc and i'm testing it on my
local.
It seems its sending that preflight OPTIONS and coming back with 401 still
On Tue, Aug 18, 2015 at 10:48 AM, Fadi Abdin <fadiabdeen(a)gmail.com> wrote:
I'm still working on it :( .. i had to give the network guys few
ip
addresses to whitelist so i can mvn install .. ... almost there.
On Tue, Aug 18, 2015 at 9:46 AM, Marc Savy <marc.savy(a)redhat.com> wrote:
> My pleasure! Did it work?
>
> On 17/08/2015 16:38, Fadi Abdin wrote:
>
>> cool .. you're the man ;)
>>
>>
>> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy <marc.savy(a)redhat.com
>> <mailto:marc.savy@redhat.com>> wrote:
>>
>> I'm actually testing the fix right now. It will land both on the
>> 1.2.x
>> branch and the 1.1.x branch shortly. You should be able to test it
>> out
>> in a short while: I'll send you an email when it's available.
>>
>> On 17/08/2015 16:23, Fadi Abdin wrote:
>>
>> Thank you Marc,
>> Is there a work around that you can think of ?
>> I'm doing it with angularjs , very simple
>>
>> $http({method: 'GET', url:
'http://server/apiman-gateway/service
>> ',
>> headers: {
>> 'Authorization': 'Bearer XXXXXXXXXXXXX'}
>> });
>>
>> I assume you will fix it in the new version , right?
>>
>>
>>
>> On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
>> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
>> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>>
>> wrote:
>>
>> Hi,
>>
>> This is related to the JIRA I linked you to
>> (https://issues.jboss.org/browse/APIMAN-516). Because of
>> the way the
>> policy chain currently works the behaviour of CORS is
>> invalid in a
>> few very specific cases (e.g. when you stack it with an auth
>> policy). I'll let you know when it's fixed.
>>
>> Regards,
>> Marc
>>
>> On 17/08/2015 15:44, Fadi Abdin wrote:
>>
>> I have a problem in calling a service in apiman-gateway
>> with the
>> Authorization: Bearer <token> in the header.
>>
>> It seems to preflight OPTIONS and return
>>
>> 1.
>> X-Policy-Failure-Message:
>> OAuth2 'Authorization' header or
'access_token'
>> query
>> parameter must
>> be provided.
>>
>> I am sending the bearer token with the request and i
>> make sure
>> in the
>> preflight its sent in the request.
>>
>> 1.
>> Access-Control-Request-Headers:
>> accept, authorization
>>
>> Does anyone know if there Is something i'm missing ?
>> do i need
>> to get
>> authorization enabled or added anywhere ? as a side
>> note i have
>> below in
>> my api as well:
>>
>> response.setHeader("Access-Control-Allow-Headers",
>> "Authorization");
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
>> <mailto:Apiman-user@lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>>
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>
>>
>>
>>
>>
>>
>
4:53 a.m.
I replicated your set up as far as I could, and I couldn't replicate your issue
(perhaps your CORS setup is wrong?). Please see the JIRA comments and screenshots -
https://issues.jboss.org/browse/APIMAN-516
Either way, I also fixed a bug unrelated to your problem, so please re-build the plugins
before trying again :-).
On 18/08/2015 19:25, Fadi Abdin wrote:
It did not work .
I setup everything they way you told me Marc and i'm testing it on my
local.
It seems its sending that preflight OPTIONS and coming back with 401 still
On Tue, Aug 18, 2015 at 10:48 AM, Fadi Abdin <fadiabdeen(a)gmail.com
<mailto:fadiabdeen@gmail.com>> wrote:
I'm still working on it :( .. i had to give the network guys few ip
addresses to whitelist so i can mvn install .. ... almost there.
On Tue, Aug 18, 2015 at 9:46 AM, Marc Savy <marc.savy(a)redhat.com
<mailto:marc.savy@redhat.com>> wrote:
My pleasure! Did it work?
On 17/08/2015 16:38, Fadi Abdin wrote:
cool .. you're the man ;)
On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy
<marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>>
wrote:
I'm actually testing the fix right now. It will land
both on the 1.2.x
branch and the 1.1.x branch shortly. You should be able
to test it out
in a short while: I'll send you an email when it's
available.
On 17/08/2015 16:23, Fadi Abdin wrote:
Thank you Marc,
Is there a work around that you can think of ?
I'm doing it with angularjs , very simple
$http({method: 'GET', url:
'http://server/apiman-gateway/service',
headers: {
'Authorization': 'Bearer XXXXXXXXXXXXX'}
});
I assume you will fix it in the new version , right?
On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
<marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>
<mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>>> wrote:
Hi,
This is related to the JIRA I linked you to
(https://issues.jboss.org/browse/APIMAN-516).
Because of
the way the
policy chain currently works the behaviour of
CORS is
invalid in a
few very specific cases (e.g. when you stack
it with an auth
policy). I'll let you know when it's fixed.
Regards,
Marc
On 17/08/2015 15:44, Fadi Abdin wrote:
I have a problem in calling a service in
apiman-gateway
with the
Authorization: Bearer <token> in the header.
It seems to preflight OPTIONS and return
1.
X-Policy-Failure-Message:
OAuth2 'Authorization' header or
'access_token' query
parameter must
be provided.
I am sending the bearer token with the
request and i
make sure
in the
preflight its sent in the request.
1.
Access-Control-Request-Headers:
accept, authorization
Does anyone know if there Is something i'm
missing ?
do i need
to get
authorization enabled or added anywhere ?
as a side
note i have
below in
my api as well:
response.setHeader("Access-Control-Allow-Headers",
"Authorization");
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>>
https://lists.jboss.org/mailman/listinfo/apiman-user
8:02 a.m.
So what it seems like is that we have to use CORS Policy and add it before
the Keycloak authentication policy in order for my preflight to pass ..
thats the part i was missing completely . i'm not sure if its should be
considered a bug or flexibility to do what we want .. But thanks for the
explaination Marc.
Anyway .. i'm still having a problem with CORS Policy, probably I just dont
have the latest code. i added some details to the JIRA ticket
On Wed, Aug 19, 2015 at 5:53 AM, Marc Savy <marc.savy(a)redhat.com> wrote:
I replicated your set up as far as I could, and I couldn't
replicate your
issue (perhaps your CORS setup is wrong?). Please see the JIRA comments and
screenshots - https://issues.jboss.org/browse/APIMAN-516
Either way, I also fixed a bug unrelated to your problem, so please
re-build the plugins before trying again :-).
On 18/08/2015 19:25, Fadi Abdin wrote:
> It did not work .
>
> I setup everything they way you told me Marc and i'm testing it on my
> local.
> It seems its sending that preflight OPTIONS and coming back with 401 still
>
> On Tue, Aug 18, 2015 at 10:48 AM, Fadi Abdin <fadiabdeen(a)gmail.com
> <mailto:fadiabdeen@gmail.com>> wrote:
>
> I'm still working on it :( .. i had to give the network guys few ip
> addresses to whitelist so i can mvn install .. ... almost there.
>
> On Tue, Aug 18, 2015 at 9:46 AM, Marc Savy <marc.savy(a)redhat.com
> <mailto:marc.savy@redhat.com>> wrote:
>
> My pleasure! Did it work?
>
> On 17/08/2015 16:38, Fadi Abdin wrote:
>
> cool .. you're the man ;)
>
>
> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy
> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>>
> wrote:
>
> I'm actually testing the fix right now. It will land
> both on the 1.2.x
> branch and the 1.1.x branch shortly. You should be able
> to test it out
> in a short while: I'll send you an email when it's
> available.
>
> On 17/08/2015 16:23, Fadi Abdin wrote:
>
> Thank you Marc,
> Is there a work around that you can think of ?
> I'm doing it with angularjs , very simple
>
> $http({method: 'GET', url:
> 'http://server/apiman-gateway/service',
> headers: {
> 'Authorization': 'Bearer XXXXXXXXXXXXX'}
> });
>
> I assume you will fix it in the new version , right?
>
>
>
> On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
> <mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>
> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>>>> wrote:
>
> Hi,
>
> This is related to the JIRA I linked you to
> (https://issues.jboss.org/browse/APIMAN-516).
> Because of
> the way the
> policy chain currently works the behaviour of
> CORS is
> invalid in a
> few very specific cases (e.g. when you stack
> it with an auth
> policy). I'll let you know when it's fixed.
>
> Regards,
> Marc
>
> On 17/08/2015 15:44, Fadi Abdin wrote:
>
> I have a problem in calling a service in
> apiman-gateway
> with the
> Authorization: Bearer <token> in the header.
>
> It seems to preflight OPTIONS and return
>
> 1.
> X-Policy-Failure-Message:
> OAuth2 'Authorization' header or
> 'access_token' query
> parameter must
> be provided.
>
> I am sending the bearer token with the
> request and i
> make sure
> in the
> preflight its sent in the request.
>
> 1.
> Access-Control-Request-Headers:
> accept, authorization
>
> Does anyone know if there Is something i'm
> missing ?
> do i need
> to get
> authorization enabled or added anywhere ?
> as a side
> note i have
> below in
> my api as well:
>
>
> response.setHeader("Access-Control-Allow-Headers",
> "Authorization");
>
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>>
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
>
>
>
>
>
>
>
8:09 a.m.
What you're doing will always require a CORS preflight request (due to the non-simple
headers), and I'm not sure it makes sense for us as an API gateway to funnel through
CORS Preflight requests to the service by default. It complicates things when you start
thinking about metering, security, etc.
Eric, what do you think?
On 19/08/2015 14:02, Fadi Abdin wrote:
So what it seems like is that we have to use CORS Policy and add it
before the Keycloak authentication policy in order for my preflight to
pass .. thats the part i was missing completely . i'm not sure if its
should be considered a bug or flexibility to do what we want .. But
thanks for the explaination Marc.
Anyway .. i'm still having a problem with CORS Policy, probably I just
dont have the latest code. i added some details to the JIRA ticket
On Wed, Aug 19, 2015 at 5:53 AM, Marc Savy <marc.savy(a)redhat.com
<mailto:marc.savy@redhat.com>> wrote:
I replicated your set up as far as I could, and I couldn't replicate
your issue (perhaps your CORS setup is wrong?). Please see the JIRA
comments and screenshots - https://issues.jboss.org/browse/APIMAN-516
Either way, I also fixed a bug unrelated to your problem, so please
re-build the plugins before trying again :-).
On 18/08/2015 19:25, Fadi Abdin wrote:
It did not work .
I setup everything they way you told me Marc and i'm testing it
on my
local.
It seems its sending that preflight OPTIONS and coming back with
401 still
On Tue, Aug 18, 2015 at 10:48 AM, Fadi Abdin
<fadiabdeen(a)gmail.com <mailto:fadiabdeen@gmail.com>
<mailto:fadiabdeen@gmail.com <mailto:fadiabdeen@gmail.com>>>
wrote:
I'm still working on it :( .. i had to give the network
guys few ip
addresses to whitelist so i can mvn install .. ... almost
there.
On Tue, Aug 18, 2015 at 9:46 AM, Marc Savy
<marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>> wrote:
My pleasure! Did it work?
On 17/08/2015 16:38, Fadi Abdin wrote:
cool .. you're the man ;)
On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy
<marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>
<mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>>>
wrote:
I'm actually testing the fix right now. It
will land
both on the 1.2.x
branch and the 1.1.x branch shortly. You
should be able
to test it out
in a short while: I'll send you an email when it's
available.
On 17/08/2015 16:23, Fadi Abdin wrote:
Thank you Marc,
Is there a work around that you can think of ?
I'm doing it with angularjs , very simple
$http({method: 'GET', url:
'http://server/apiman-gateway/service',
headers: {
'Authorization': 'Bearer
XXXXXXXXXXXXX'}
});
I assume you will fix it in the new
version , right?
On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
<marc.savy(a)redhat.com
<mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>
<mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>>
<mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>>>> wrote:
Hi,
This is related to the JIRA I linked
you to
(https://issues.jboss.org/browse/APIMAN-516).
Because of
the way the
policy chain currently works the
behaviour of
CORS is
invalid in a
few very specific cases (e.g. when
you stack
it with an auth
policy). I'll let you know when it's
fixed.
Regards,
Marc
On 17/08/2015 15:44, Fadi Abdin wrote:
I have a problem in calling a
service in
apiman-gateway
with the
Authorization: Bearer <token> in
the header.
It seems to preflight OPTIONS and
return
1.
X-Policy-Failure-Message:
OAuth2 'Authorization' header or
'access_token' query
parameter must
be provided.
I am sending the bearer token
with the
request and i
make sure
in the
preflight its sent in the request.
1.
Access-Control-Request-Headers:
accept, authorization
Does anyone know if there Is
something i'm
missing ?
do i need
to get
authorization enabled or added
anywhere ?
as a side
note i have
below in
my api as well:
response.setHeader("Access-Control-Allow-Headers",
"Authorization");
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>
<mailto:Apiman-user@lists.jboss.org
<mailto:Apiman-user@lists.jboss.org>>>>
https://lists.jboss.org/mailman/listinfo/apiman-user
8:16 a.m.
I think that if apiman is being asked to do Authentication *and* CORS is
required by the client, then apiman will have to do both.
I think that's desirable anyway - it allows the back end service
implementation to not worry about supporting CORS. It's a win-win.
-Eric
On 8/19/2015 9:09 AM, Marc Savy wrote:
What you're doing will always require a CORS preflight request
(due to the non-simple headers), and I'm not sure it makes sense for us as an API
gateway to funnel through CORS Preflight requests to the service by default. It
complicates things when you start thinking about metering, security, etc.
Eric, what do you think?
On 19/08/2015 14:02, Fadi Abdin wrote:
> So what it seems like is that we have to use CORS Policy and add it
> before the Keycloak authentication policy in order for my preflight to
> pass .. thats the part i was missing completely . i'm not sure if its
> should be considered a bug or flexibility to do what we want .. But
> thanks for the explaination Marc.
>
> Anyway .. i'm still having a problem with CORS Policy, probably I just
> dont have the latest code. i added some details to the JIRA ticket
>
> On Wed, Aug 19, 2015 at 5:53 AM, Marc Savy <marc.savy(a)redhat.com
> <mailto:marc.savy@redhat.com>> wrote:
>
> I replicated your set up as far as I could, and I couldn't replicate
> your issue (perhaps your CORS setup is wrong?). Please see the JIRA
> comments and screenshots - https://issues.jboss.org/browse/APIMAN-516
>
> Either way, I also fixed a bug unrelated to your problem, so please
> re-build the plugins before trying again :-).
>
> On 18/08/2015 19:25, Fadi Abdin wrote:
>
> It did not work .
>
> I setup everything they way you told me Marc and i'm testing it
> on my
> local.
> It seems its sending that preflight OPTIONS and coming back with
> 401 still
>
> On Tue, Aug 18, 2015 at 10:48 AM, Fadi Abdin
> <fadiabdeen(a)gmail.com <mailto:fadiabdeen@gmail.com>
> <mailto:fadiabdeen@gmail.com <mailto:fadiabdeen@gmail.com>>>
wrote:
>
> I'm still working on it :( .. i had to give the network
> guys few ip
> addresses to whitelist so i can mvn install .. ... almost
> there.
>
> On Tue, Aug 18, 2015 at 9:46 AM, Marc Savy
> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>>> wrote:
>
> My pleasure! Did it work?
>
> On 17/08/2015 16:38, Fadi Abdin wrote:
>
> cool .. you're the man ;)
>
>
> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy
> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
> <mailto:marc.savy@redhat.com <mailto:marc.savy@redhat.com>>
> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>>>>
> wrote:
>
> I'm actually testing the fix right now. It
> will land
> both on the 1.2.x
> branch and the 1.1.x branch shortly. You
> should be able
> to test it out
> in a short while: I'll send you an email when
it's
> available.
>
> On 17/08/2015 16:23, Fadi Abdin wrote:
>
> Thank you Marc,
> Is there a work around that you can think of ?
> I'm doing it with angularjs , very simple
>
> $http({method: 'GET', url:
> 'http://server/apiman-gateway/service',
> headers: {
> 'Authorization': 'Bearer
XXXXXXXXXXXXX'}
> });
>
> I assume you will fix it in the new
> version , right?
>
>
>
> On Mon, Aug 17, 2015 at 10:52 AM, Marc Savy
> <marc.savy(a)redhat.com
> <mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>>
> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>>>
> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>
> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>
> <mailto:marc.savy@redhat.com
> <mailto:marc.savy@redhat.com>>>>> wrote:
>
> Hi,
>
> This is related to the JIRA I linked
> you to
>
> (https://issues.jboss.org/browse/APIMAN-516).
> Because of
> the way the
> policy chain currently works the
> behaviour of
> CORS is
> invalid in a
> few very specific cases (e.g. when
> you stack
> it with an auth
> policy). I'll let you know when it's
> fixed.
>
> Regards,
> Marc
>
> On 17/08/2015 15:44, Fadi Abdin wrote:
>
> I have a problem in calling a
> service in
> apiman-gateway
> with the
> Authorization: Bearer <token> in
> the header.
>
> It seems to preflight OPTIONS and
> return
>
> 1.
> X-Policy-Failure-Message:
> OAuth2 'Authorization' header
or
> 'access_token' query
> parameter must
> be provided.
>
> I am sending the bearer token
> with the
> request and i
> make sure
> in the
> preflight its sent in the request.
>
> 1.
> Access-Control-Request-Headers:
> accept, authorization
>
> Does anyone know if there Is
> something i'm
> missing ?
> do i need
> to get
> authorization enabled or added
> anywhere ?
> as a side
> note i have
> below in
> my api as well:
>
>
> response.setHeader("Access-Control-Allow-Headers",
> "Authorization");
>
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>
> <mailto:Apiman-user@lists.jboss.org
> <mailto:Apiman-user@lists.jboss.org>>>>
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
>
>
>
>
>
>
>
>
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user
10:23 a.m.
I think case being suggested here is slightly different -
This is one where someone has selected an Auth policy on the gateway, but *not* a CORS
policy - instead their back-end service supports CORS and they want the service to handle
the preflight request directly. Should we pipeline the CORS preflight request through to
the backend in that case (i.e. bypass auth)? I'd say no, probably.
Perhaps that's what you were getting at already!
On 19/08/2015 14:16, Eric Wittmann wrote:
I think that if apiman is being asked to do Authentication *and* CORS
is
required by the client, then apiman will have to do both.
I think that's desirable anyway - it allows the back end service
implementation to not worry about supporting CORS. It's a win-win.
-Eric
On 8/19/2015 9:09 AM, Marc Savy wrote:
> What you're doing will always require a CORS preflight request (due to
> the non-simple headers), and I'm not sure it makes sense for us as an
> API gateway to funnel through CORS Preflight requests to the service
> by default. It complicates things when you start thinking about
> metering, security, etc.
>
> Eric, what do you think?
>
> On 19/08/2015 14:02, Fadi Abdin wrote:
>> So what it seems like is that we have to use CORS Policy and add it
>> before the Keycloak authentication policy in order for my preflight to
>> pass .. thats the part i was missing completely . i'm not sure if its
>> should be considered a bug or flexibility to do what we want .. But
>> thanks for the explaination Marc.
>>
>> Anyway .. i'm still having a problem with CORS Policy, probably I just
>> dont have the latest code. i added some details to the JIRA ticket
>>
>> On Wed, Aug 19, 2015 at 5:53 AM, Marc Savy <marc.savy(a)redhat.com
>> <mailto:marc.savy@redhat.com>> wrote:
>>
>> I replicated your set up as far as I could, and I couldn't
>> replicate
>> your issue (perhaps your CORS setup is wrong?). Please see the JIRA
>> comments and screenshots -
>> https://issues.jboss.org/browse/APIMAN-516
>>
>> Either way, I also fixed a bug unrelated to your problem, so please
>> re-build the plugins before trying again :-).
>>
>> On 18/08/2015 19:25, Fadi Abdin wrote:
>>
>> It did not work .
>>
>> I setup everything they way you told me Marc and i'm testing it
>> on my
>> local.
>> It seems its sending that preflight OPTIONS and coming back
>> with
>> 401 still
>>
>> On Tue, Aug 18, 2015 at 10:48 AM, Fadi Abdin
>> <fadiabdeen(a)gmail.com <mailto:fadiabdeen@gmail.com>
>> <mailto:fadiabdeen@gmail.com
<mailto:fadiabdeen@gmail.com>>>
>> wrote:
>>
>> I'm still working on it :( .. i had to give the network
>> guys few ip
>> addresses to whitelist so i can mvn install .. ... almost
>> there.
>>
>> On Tue, Aug 18, 2015 at 9:46 AM, Marc Savy
>> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
>> <mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com>>> wrote:
>>
>> My pleasure! Did it work?
>>
>> On 17/08/2015 16:38, Fadi Abdin wrote:
>>
>> cool .. you're the man ;)
>>
>>
>> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy
>> <marc.savy(a)redhat.com
>> <mailto:marc.savy@redhat.com>
>> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>
>> <mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com>>>>
>> wrote:
>>
>> I'm actually testing the fix right now. It
>> will land
>> both on the 1.2.x
>> branch and the 1.1.x branch shortly. You
>> should be able
>> to test it out
>> in a short while: I'll send you an email
>> when it's
>> available.
>>
>> On 17/08/2015 16:23, Fadi Abdin wrote:
>>
>> Thank you Marc,
>> Is there a work around that you can
>> think of ?
>> I'm doing it with angularjs , very
>> simple
>>
>> $http({method: 'GET', url:
>> 'http://server/apiman-gateway/service',
>> headers: {
>> 'Authorization': 'Bearer
>> XXXXXXXXXXXXX'}
>> });
>>
>> I assume you will fix it in the new
>> version , right?
>>
>>
>>
>> On Mon, Aug 17, 2015 at 10:52 AM, Marc
>> Savy
>> <marc.savy(a)redhat.com
>> <mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com>>
>> <mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com> <mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com>>>
>> <mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com>
>> <mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com>>
<mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com>
>> <mailto:marc.savy@redhat.com
>> <mailto:marc.savy@redhat.com>>>>> wrote:
>>
>> Hi,
>>
>> This is related to the JIRA I linked
>> you to
>>
>> (https://issues.jboss.org/browse/APIMAN-516).
>> Because of
>> the way the
>> policy chain currently works the
>> behaviour of
>> CORS is
>> invalid in a
>> few very specific cases (e.g. when
>> you stack
>> it with an auth
>> policy). I'll let you know when
it's
>> fixed.
>>
>> Regards,
>> Marc
>>
>> On 17/08/2015 15:44, Fadi Abdin
>> wrote:
>>
>> I have a problem in calling a
>> service in
>> apiman-gateway
>> with the
>> Authorization: Bearer <token> in
>> the header.
>>
>> It seems to preflight OPTIONS
>> and
>> return
>>
>> 1.
>> X-Policy-Failure-Message:
>> OAuth2 'Authorization'
>> header or
>> 'access_token' query
>> parameter must
>> be provided.
>>
>> I am sending the bearer token
>> with the
>> request and i
>> make sure
>> in the
>> preflight its sent in the
>> request.
>>
>> 1.
>>
>> Access-Control-Request-Headers:
>> accept, authorization
>>
>> Does anyone know if there Is
>> something i'm
>> missing ?
>> do i need
>> to get
>> authorization enabled or added
>> anywhere ?
>> as a side
>> note i have
>> below in
>> my api as well:
>>
>>
>>
>> response.setHeader("Access-Control-Allow-Headers",
>> "Authorization");
>>
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user(a)lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>
>> <mailto:Apiman-user@lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>>
>> <mailto:Apiman-user@lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>
>> <mailto:Apiman-user@lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>>>
>> <mailto:Apiman-user@lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>
>> <mailto:Apiman-user@lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>>
>> <mailto:Apiman-user@lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>
>> <mailto:Apiman-user@lists.jboss.org
>> <mailto:Apiman-user@lists.jboss.org>>>>
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
10:55 a.m.
That is exactly what I was getting at. If you have apiman performing
authentication, then apiman MUST ALSO perform CORS for you.
Specifically for the reason you say: we don't want to skip
authentication for OPTIONS requests.
That said, we *could* add another option to all the authentication
policies, allowing auth to be skipped for specific VERBs. That could be
a reasonable feature. I don't think I'm in favor of it though.
Instead, CORS functionality should be moved out of the back-end system
and handled in apiman.
-Eric
On 8/19/2015 11:23 AM, Marc Savy wrote:
I think case being suggested here is slightly different -
This is one where someone has selected an Auth policy on the gateway,
but *not* a CORS policy - instead their back-end service supports CORS
and they want the service to handle the preflight request directly.
Should we pipeline the CORS preflight request through to the backend in
that case (i.e. bypass auth)? I'd say no, probably.
Perhaps that's what you were getting at already!
On 19/08/2015 14:16, Eric Wittmann wrote:
> I think that if apiman is being asked to do Authentication *and* CORS is
> required by the client, then apiman will have to do both.
>
> I think that's desirable anyway - it allows the back end service
> implementation to not worry about supporting CORS. It's a win-win.
>
> -Eric
>
> On 8/19/2015 9:09 AM, Marc Savy wrote:
> > What you're doing will always require a CORS preflight request (due to
> > the non-simple headers), and I'm not sure it makes sense for us as an
> > API gateway to funnel through CORS Preflight requests to the service
> > by default. It complicates things when you start thinking about
> > metering, security, etc.
> >
> > Eric, what do you think?
> >
> > On 19/08/2015 14:02, Fadi Abdin wrote:
> >> So what it seems like is that we have to use CORS Policy and add it
> >> before the Keycloak authentication policy in order for my preflight to
> >> pass .. thats the part i was missing completely . i'm not sure if its
> >> should be considered a bug or flexibility to do what we want .. But
> >> thanks for the explaination Marc.
> >>
> >> Anyway .. i'm still having a problem with CORS Policy, probably I just
> >> dont have the latest code. i added some details to the JIRA ticket
> >>
> >> On Wed, Aug 19, 2015 at 5:53 AM, Marc Savy <marc.savy(a)redhat.com
> >> <mailto:marc.savy@redhat.com>> wrote:
> >>
> >> I replicated your set up as far as I could, and I couldn't
> >> replicate
> >> your issue (perhaps your CORS setup is wrong?). Please see the
> JIRA
> >> comments and screenshots -
> >> https://issues.jboss.org/browse/APIMAN-516
> >>
> >> Either way, I also fixed a bug unrelated to your problem, so
> please
> >> re-build the plugins before trying again :-).
> >>
> >> On 18/08/2015 19:25, Fadi Abdin wrote:
> >>
> >> It did not work .
> >>
> >> I setup everything they way you told me Marc and i'm
> testing it
> >> on my
> >> local.
> >> It seems its sending that preflight OPTIONS and coming back
> >> with
> >> 401 still
> >>
> >> On Tue, Aug 18, 2015 at 10:48 AM, Fadi Abdin
> >> <fadiabdeen(a)gmail.com <mailto:fadiabdeen@gmail.com>
> >> <mailto:fadiabdeen@gmail.com
<mailto:fadiabdeen@gmail.com>>>
> >> wrote:
> >>
> >> I'm still working on it :( .. i had to give the network
> >> guys few ip
> >> addresses to whitelist so i can mvn install .. ...
> almost
> >> there.
> >>
> >> On Tue, Aug 18, 2015 at 9:46 AM, Marc Savy
> >> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
> >> <mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>>> wrote:
> >>
> >> My pleasure! Did it work?
> >>
> >> On 17/08/2015 16:38, Fadi Abdin wrote:
> >>
> >> cool .. you're the man ;)
> >>
> >>
> >> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy
> >> <marc.savy(a)redhat.com
> >> <mailto:marc.savy@redhat.com>
> >> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>
> >> <mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>>>>
> >> wrote:
> >>
> >> I'm actually testing the fix right now. It
> >> will land
> >> both on the 1.2.x
> >> branch and the 1.1.x branch shortly. You
> >> should be able
> >> to test it out
> >> in a short while: I'll send you an email
> >> when it's
> >> available.
> >>
> >> On 17/08/2015 16:23, Fadi Abdin wrote:
> >>
> >> Thank you Marc,
> >> Is there a work around that you can
> >> think of ?
> >> I'm doing it with angularjs , very
> >> simple
> >>
> >> $http({method: 'GET', url:
> >> 'http://server/apiman-gateway/service',
> >> headers: {
> >> 'Authorization': 'Bearer
> >> XXXXXXXXXXXXX'}
> >> });
> >>
> >> I assume you will fix it in the new
> >> version , right?
> >>
> >>
> >>
> >> On Mon, Aug 17, 2015 at 10:52 AM, Marc
> >> Savy
> >> <marc.savy(a)redhat.com
> >> <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>>
> >> <mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>>>
> >> <mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>
> >> <mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>>
<mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>
> >> <mailto:marc.savy@redhat.com
> >> <mailto:marc.savy@redhat.com>>>>> wrote:
> >>
> >> Hi,
> >>
> >> This is related to the JIRA I
> linked
> >> you to
> >>
> >> (https://issues.jboss.org/browse/APIMAN-516).
> >> Because of
> >> the way the
> >> policy chain currently works the
> >> behaviour of
> >> CORS is
> >> invalid in a
> >> few very specific cases (e.g. when
> >> you stack
> >> it with an auth
> >> policy). I'll let you know when
> it's
> >> fixed.
> >>
> >> Regards,
> >> Marc
> >>
> >> On 17/08/2015 15:44, Fadi Abdin
> >> wrote:
> >>
> >> I have a problem in calling a
> >> service in
> >> apiman-gateway
> >> with the
> >> Authorization: Bearer
> <token> in
> >> the header.
> >>
> >> It seems to preflight OPTIONS
> >> and
> >> return
> >>
> >> 1.
> >> X-Policy-Failure-Message:
> >> OAuth2 'Authorization'
> >> header or
> >> 'access_token' query
> >> parameter must
> >> be provided.
> >>
> >> I am sending the bearer token
> >> with the
> >> request and i
> >> make sure
> >> in the
> >> preflight its sent in the
> >> request.
> >>
> >> 1.
> >>
> >> Access-Control-Request-Headers:
> >> accept, authorization
> >>
> >> Does anyone know if there Is
> >> something i'm
> >> missing ?
> >> do i need
> >> to get
> >> authorization enabled or added
> >> anywhere ?
> >> as a side
> >> note i have
> >> below in
> >> my api as well:
> >>
> >>
> >>
> >> response.setHeader("Access-Control-Allow-Headers",
> >> "Authorization");
> >>
> >>
> >>
> >>
> _______________________________________________
> >> Apiman-user mailing list
> >> Apiman-user(a)lists.jboss.org
> >> <mailto:Apiman-user@lists.jboss.org>
> >> <mailto:Apiman-user@lists.jboss.org
> >> <mailto:Apiman-user@lists.jboss.org>>
> >> <mailto:Apiman-user@lists.jboss.org
> >> <mailto:Apiman-user@lists.jboss.org>
> >> <mailto:Apiman-user@lists.jboss.org
> >> <mailto:Apiman-user@lists.jboss.org>>>
> >> <mailto:Apiman-user@lists.jboss.org
> >> <mailto:Apiman-user@lists.jboss.org>
> >> <mailto:Apiman-user@lists.jboss.org
> >> <mailto:Apiman-user@lists.jboss.org>>
> >> <mailto:Apiman-user@lists.jboss.org
> >> <mailto:Apiman-user@lists.jboss.org>
> >> <mailto:Apiman-user@lists.jboss.org
> >> <mailto:Apiman-user@lists.jboss.org>>>>
> >> https://lists.jboss.org/mailman/listinfo/apiman-user
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> > _______________________________________________
> > Apiman-user mailing list
> > Apiman-user(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/apiman-user
> >
10:58 a.m.
I agree - I don't see any compelling reason to add that kind of complexity for that
case. I'm willing to be convinced, though.
On 19/08/2015 16:55, Eric Wittmann wrote:
That is exactly what I was getting at. If you have apiman
performing
authentication, then apiman MUST ALSO perform CORS for you. Specifically
for the reason you say: we don't want to skip authentication for
OPTIONS requests.
That said, we *could* add another option to all the authentication
policies, allowing auth to be skipped for specific VERBs. That could be
a reasonable feature. I don't think I'm in favor of it though.
Instead, CORS functionality should be moved out of the back-end system
and handled in apiman.
-Eric
On 8/19/2015 11:23 AM, Marc Savy wrote:
> I think case being suggested here is slightly different -
>
> This is one where someone has selected an Auth policy on the gateway,
> but *not* a CORS policy - instead their back-end service supports CORS
> and they want the service to handle the preflight request directly.
> Should we pipeline the CORS preflight request through to the backend in
> that case (i.e. bypass auth)? I'd say no, probably.
>
> Perhaps that's what you were getting at already!
>
> On 19/08/2015 14:16, Eric Wittmann wrote:
>> I think that if apiman is being asked to do Authentication *and* CORS is
>> required by the client, then apiman will have to do both.
>>
>> I think that's desirable anyway - it allows the back end service
>> implementation to not worry about supporting CORS. It's a win-win.
>>
>> -Eric
>>
>> On 8/19/2015 9:09 AM, Marc Savy wrote:
>> > What you're doing will always require a CORS preflight request (due to
>> > the non-simple headers), and I'm not sure it makes sense for us as an
>> > API gateway to funnel through CORS Preflight requests to the service
>> > by default. It complicates things when you start thinking about
>> > metering, security, etc.
>> >
>> > Eric, what do you think?
>> >
>> > On 19/08/2015 14:02, Fadi Abdin wrote:
>> >> So what it seems like is that we have to use CORS Policy and add it
>> >> before the Keycloak authentication policy in order for my
>> preflight to
>> >> pass .. thats the part i was missing completely . i'm not sure if
its
>> >> should be considered a bug or flexibility to do what we want .. But
>> >> thanks for the explaination Marc.
>> >>
>> >> Anyway .. i'm still having a problem with CORS Policy, probably I
>> just
>> >> dont have the latest code. i added some details to the JIRA ticket
>> >>
>> >> On Wed, Aug 19, 2015 at 5:53 AM, Marc Savy <marc.savy(a)redhat.com
>> >> <mailto:marc.savy@redhat.com>> wrote:
>> >>
>> >> I replicated your set up as far as I could, and I couldn't
>> >> replicate
>> >> your issue (perhaps your CORS setup is wrong?). Please see the
>> JIRA
>> >> comments and screenshots -
>> >> https://issues.jboss.org/browse/APIMAN-516
>> >>
>> >> Either way, I also fixed a bug unrelated to your problem, so
>> please
>> >> re-build the plugins before trying again :-).
>> >>
>> >> On 18/08/2015 19:25, Fadi Abdin wrote:
>> >>
>> >> It did not work .
>> >>
>> >> I setup everything they way you told me Marc and i'm
>> testing it
>> >> on my
>> >> local.
>> >> It seems its sending that preflight OPTIONS and coming back
>> >> with
>> >> 401 still
>> >>
>> >> On Tue, Aug 18, 2015 at 10:48 AM, Fadi Abdin
>> >> <fadiabdeen(a)gmail.com <mailto:fadiabdeen@gmail.com>
>> >> <mailto:fadiabdeen@gmail.com
<mailto:fadiabdeen@gmail.com>>>
>> >> wrote:
>> >>
>> >> I'm still working on it :( .. i had to give the
network
>> >> guys few ip
>> >> addresses to whitelist so i can mvn install .. ...
>> almost
>> >> there.
>> >>
>> >> On Tue, Aug 18, 2015 at 9:46 AM, Marc Savy
>> >> <marc.savy(a)redhat.com <mailto:marc.savy@redhat.com>
>> >> <mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>>> wrote:
>> >>
>> >> My pleasure! Did it work?
>> >>
>> >> On 17/08/2015 16:38, Fadi Abdin wrote:
>> >>
>> >> cool .. you're the man ;)
>> >>
>> >>
>> >> On Mon, Aug 17, 2015 at 11:37 AM, Marc Savy
>> >> <marc.savy(a)redhat.com
>> >> <mailto:marc.savy@redhat.com>
>> >> <mailto:marc.savy@redhat.com
<mailto:marc.savy@redhat.com>>
>> >> <mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>>>>
>> >> wrote:
>> >>
>> >> I'm actually testing the fix right now.
It
>> >> will land
>> >> both on the 1.2.x
>> >> branch and the 1.1.x branch shortly. You
>> >> should be able
>> >> to test it out
>> >> in a short while: I'll send you an
email
>> >> when it's
>> >> available.
>> >>
>> >> On 17/08/2015 16:23, Fadi Abdin wrote:
>> >>
>> >> Thank you Marc,
>> >> Is there a work around that you can
>> >> think of ?
>> >> I'm doing it with angularjs , very
>> >> simple
>> >>
>> >> $http({method: 'GET', url:
>> >> 'http://server/apiman-gateway/service',
>> >> headers: {
>> >> 'Authorization':
'Bearer
>> >> XXXXXXXXXXXXX'}
>> >> });
>> >>
>> >> I assume you will fix it in the new
>> >> version , right?
>> >>
>> >>
>> >>
>> >> On Mon, Aug 17, 2015 at 10:52 AM, Marc
>> >> Savy
>> >> <marc.savy(a)redhat.com
>> >> <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>>
>> >> <mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>
<mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>>>
>> >> <mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>
>> >> <mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>>
<mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>
>> >> <mailto:marc.savy@redhat.com
>> >> <mailto:marc.savy@redhat.com>>>>> wrote:
>> >>
>> >> Hi,
>> >>
>> >> This is related to the JIRA I
>> linked
>> >> you to
>> >>
>> >> (https://issues.jboss.org/browse/APIMAN-516).
>> >> Because of
>> >> the way the
>> >> policy chain currently works the
>> >> behaviour of
>> >> CORS is
>> >> invalid in a
>> >> few very specific cases (e.g.
>> when
>> >> you stack
>> >> it with an auth
>> >> policy). I'll let you know
when
>> it's
>> >> fixed.
>> >>
>> >> Regards,
>> >> Marc
>> >>
>> >> On 17/08/2015 15:44, Fadi Abdin
>> >> wrote:
>> >>
>> >> I have a problem in calling a
>> >> service in
>> >> apiman-gateway
>> >> with the
>> >> Authorization: Bearer
>> <token> in
>> >> the header.
>> >>
>> >> It seems to preflight OPTIONS
>> >> and
>> >> return
>> >>
>> >> 1.
>> >>
>> X-Policy-Failure-Message:
>> >> OAuth2
'Authorization'
>> >> header or
>> >> 'access_token' query
>> >> parameter must
>> >> be provided.
>> >>
>> >> I am sending the bearer token
>> >> with the
>> >> request and i
>> >> make sure
>> >> in the
>> >> preflight its sent in the
>> >> request.
>> >>
>> >> 1.
>> >>
>> >> Access-Control-Request-Headers:
>> >> accept, authorization
>> >>
>> >> Does anyone know if there Is
>> >> something i'm
>> >> missing ?
>> >> do i need
>> >> to get
>> >> authorization enabled or
>> added
>> >> anywhere ?
>> >> as a side
>> >> note i have
>> >> below in
>> >> my api as well:
>> >>
>> >>
>> >>
>> >> response.setHeader("Access-Control-Allow-Headers",
>> >> "Authorization");
>> >>
>> >>
>> >>
>> >>
>> _______________________________________________
>> >> Apiman-user mailing list
>> >> Apiman-user(a)lists.jboss.org
>> >> <mailto:Apiman-user@lists.jboss.org>
>> >> <mailto:Apiman-user@lists.jboss.org
>> >> <mailto:Apiman-user@lists.jboss.org>>
>> >> <mailto:Apiman-user@lists.jboss.org
>> >> <mailto:Apiman-user@lists.jboss.org>
>> >> <mailto:Apiman-user@lists.jboss.org
>> >> <mailto:Apiman-user@lists.jboss.org>>>
>> >> <mailto:Apiman-user@lists.jboss.org
>> >> <mailto:Apiman-user@lists.jboss.org>
>> >> <mailto:Apiman-user@lists.jboss.org
>> >> <mailto:Apiman-user@lists.jboss.org>>
>> >> <mailto:Apiman-user@lists.jboss.org
>> >> <mailto:Apiman-user@lists.jboss.org>
>> >> <mailto:Apiman-user@lists.jboss.org
>> >> <mailto:Apiman-user@lists.jboss.org>>>>
>> >> https://lists.jboss.org/mailman/listinfo/apiman-user
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> > _______________________________________________
>> > Apiman-user mailing list
>> > Apiman-user(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/apiman-user
>> >
>
3794
days inactive
3796
days old
20 comments
3 participants
participants (3)
-
Eric Wittmann -
Fadi Abdin -
Marc Savy