Natan Yellin

@encima I assume you're referring to `app_metadata` in the JWT, correct? If so, the relevant data is **not** there. It is in `user_metadata` instead which is insecure. Here is a...

@encima, sorry, I should have clarified. We are using OAuth not SAML, but does that matter in this context? (We configured the claims in the OIDC app in Azure, as...

@encima however you configure it, wont it still get written `user_metadata` in the JWT and to `raw_user_meta_data` in the `auth.users` table? In which case it doesn't matter how we configure...

Thank you, perfect.

Yes, all of the above, with explicit warnings "DO NOT USE THE raw_user_meta_data IN RLS" and "DO NOT USE user_metadata IN THE JWT IN YOUR POLICIES"

@smoug25 can you confirm if this is still happening or if it was fixed?

Weird. If you run the curl command from the robusta-runner pod, does it work? I am trying to figure out what is different about the way the runner connects.

Hi @otherguy, We have the `rate_limit` param included today. The branch adding the other changes is found [here](https://github.com/robusta-dev/robusta/compare/master...warning_event_triggerparams?expand=1#diff-7b2adb2fe8fde40be643d7f6b9eaeeb8b76e5f7793d83b6bcba5e25296b40d61) but it's been delayed in merging for now. We plan to get...

@pavangudiwada can you update the docs for `on_kubernetes_warning_event_create` (and any related triggers) to add `rate_limit`?

@otherguy reaching out to you about this on Slack.