Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Brassely David
    @brasseld
    right ?
    Youri De Bondt
    @ydbondt
    yeah
    offcourse, I could try to hook a java agent on the mgmt api and gateway
    and see what I can get out of it
    but then I need to be able to disable ES
    Brassely David
    @brasseld
    why not removing the ES reporter from the gateway ?
    Youri De Bondt
    @ydbondt
    yeah I did that
    but I can't seem to disable it from the management api
    I tried setting analytics.enabled: false
    but then I'm getting:
    12:48:55.001 [searchindexer-1] ERROR o.s.s.s.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task.
    org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'graviteeTransactionManager' available: No matching PlatformTransactionManager bean found for qualifier 'graviteeTransactionManager' - neither qualifier match nor bean name match!
    Brassely David
    @brasseld
    seems to be the same as this issue: gravitee-io/issues#945
    Youri De Bondt
    @ydbondt
    Hmm, I'll try to remove the plugin
    Gregory Marfjan
    @gmarfjan
    Hi guys, Do you have a good/bad feedback on gravitee.io/APIM connected to AWS Cognito ?
    Nicolas Géraud
    @NicolasGeraud
    I've no feedback to share. You want to secure the ui or the gateway ?
    Muthukrishnan GanapathiDharmarajan
    @muthukrishnan.dharmarajan_gitlab
    Hi all,
    Give me a solution for this issue....very urgent
    gravitee-io/issues#2636
    Thanks in advance........
    Also kindly give some replies on this gravitee-io/issues#2630
    Muthukrishnan GanapathiDharmarajan
    @muthukrishnan.dharmarajan_gitlab
    also find this question gravitee-io/issues#2637
    Nicolas Géraud
    @NicolasGeraud
    hi @muthukrishnan.dharmarajan_gitlab , you use a free and open source product. So please be patient, we have customers that pay for very urgent answers and they have priority.
    Muthukrishnan GanapathiDharmarajan
    @muthukrishnan.dharmarajan_gitlab
    @NicolasGeraud
    we are using gravitee majorly to secure our api access and at our completion of our development we may get licensed gravitee on our production as we require more security.....so kindly consider us for on business development..
    Thank you..
    krnr
    @krnr

    hi everyone,
    i couldn't find in documentation an explanation how paths work for policies

    for example, i want to use cache policy for /api/resource/:id, /api/resource, /api/resource?param1=foo, but not for /api/resource?param1=foo&param2=bar. is it possible?

    another question about cache:

    i found this pr gravitee-io/gravitee-policy-cache#2 for "invalidate cache action" (am i right?) how does it work?

    for example, i have an endpoint /api/comments?topic=1234. what should i do to invalidate cache when i

    POST /api/comments?topic=1234 
    {
      "message": "return this new one with the others instead of cached"
    }

    ?

    should i POST with X-Gravitee-Cache:refresh header?

    Brassely David
    @brasseld
    but not for /api/resource?param1=foo&param2=bar. is it possible?
    no it isn't
    krnr
    @krnr
    thank you
    Brassely David
    @brasseld
    should i POST with X-Gravitee-Cache:refresh header?
    yes
    krnr
    @krnr
    so, i surmise that /api/resource path works as /api/resource[.*] and covers /api/resource/:pk and /api/resource?with=all&params=true. am i right?
    Brassely David
    @brasseld
    absolutely !
    we are working on path, not on query-parameters
    krnr
    @krnr
    thank you once again, david! you helped me very much
    Brassely David
    @brasseld
    we have an issue to define conditional policies based on request header / params / time / ...
    but we don't find time to work on it for now
    one day, we'll be able to provide you with fine-grained policies condition :)
    krnr
    @krnr
    and let's hope that soon it comes )))
    Brassely David
    @brasseld
    ahah, I would love :)
    Gregory Marfjan
    @gmarfjan
    @NicolasGeraud , yes I would protect the UI & GW with an existing IAM (AWS cognito). Cognito allows OpenId so It could be pretty cool.
    krnr
    @krnr
    is it possible at list to distinguish list and detail endpoint for policies? /api/resource and /api/resource/123
    Brassely David
    @brasseld
    @gmarfjan we have some users here who are using Cognito as OIDC provider. don't remember who exactly but I'm pretty sure I've seen some github issues about Cognito in the past
    @gmarfjan as soon as Cognito is OIDC compliant, there is absolutely no issue to use it
    @krnr yes you can define two paths: /api/resource and /api/resource/:resource
    krnr
    @krnr
    i would use cache-key {#request.params['url']} for detail and... and what about /api/resource?query=params? how to force cache-key for use GET params precisely so that it won't influence other set of params?
    Gregory Marfjan
    @gmarfjan
    @brasseld Thx ;-)
    Brassely David
    @brasseld
    @krnr it depends how you manage others, and what do you mean by 'others'. Is others, differents application (I mean Gravitee application) ?
    krnr
    @krnr
    no, other set of params
    Brassely David
    @brasseld
    @gmarfjan you're welcome.
    krnr
    @krnr
    so that cache of /api/resource?query=foo won't mingle with /api/resource?query=bar and /api/resource?notqueryparam=baz&another=...
    Brassely David
    @brasseld
    in that cas, you just have to use the query param value as cache-key, or be part of the cache key
    krnr
    @krnr
    oh, that's nice! thank you, sir, once again
    Brassely David
    @brasseld
    yep you're welcome