I should have said, depending which one you edit, there may be no KC prefix (e.g. using
server-all's standalone.xml it won't have the kc prefix, but on
standalone-apiman.xml it does):
standalone/configuration/standalone.xml
381: <enable-cors>false</enable-cors>
Let me know how it goes.
On 14/04/2015 13:18, Marc Savy wrote:
Could you please try the following for a temporary work-around:
Edit your standalone.xml file (whichever one you're using, might be
apiman-standalone.xml) and change
- <kc:enable-cors>true</kc:enable-cors>
+ <kc:enable-cors>false</kc:enable-cors>
On 14/04/2015 10:13, Marc Savy wrote:
> Hi Alexandre,
>
> Does the error look similar to this?
https://issues.jboss.org/browse/APIMAN-384
>
> Are you using Chrome? Can you please try Firefox? It's definitely a bug, but it
seems only to trigger with certain browsers.
>
> Regards,
> Marc
>
> On 14/04/2015 01:04, Alexandre Kieling wrote:
>> 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
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user(a)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
>
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user