Search

The schema definition for logs appears to be inaccurate - Auth0 Community

5 (205) · $ 17.00 · In stock

The schema definition for logs appears to be inaccurate - Auth0 Community

Problem statement We have noticed that schema definition for tenant logs that is published in your Management API documentation shows that the response body’s scope property is of type string. However when I receive logs that have values in scope the values are always arrays of strings. I should mention that I receive these logs are processed through our custom webhook via a Log Stream. I have attached 2 screenshots to show what I’m talking about. Why is there an apparent difference

Users Import / Export extension not working - Auth0 Community

Users Import / Export extension not working - Auth0 Community

How to stream CloudWatch logs to Elasticsearch without custom code - DEV  Community

How to stream CloudWatch logs to Elasticsearch without custom code - DEV Community

Software engineering notebook – Sharing solutions to some problems that  documentation or stackoverflow did not have (at the time)…

Software engineering notebook – Sharing solutions to some problems that documentation or stackoverflow did not have (at the time)…

javascript - Access token missing from Keycloak context - Stack Overflow

javascript - Access token missing from Keycloak context - Stack Overflow

Audit Logging - Jitterbit's Success Central

Audit Logging - Jitterbit's Success Central

Fullstack app with TypeScript, Next.js, Prisma & GraphQL - Authentication

Fullstack app with TypeScript, Next.js, Prisma & GraphQL - Authentication

WebSockets Integration with KrakenD API Gateway - Enterprise Edition

WebSockets Integration with KrakenD API Gateway - Enterprise Edition

Setting up Auth0 as an 8base Authentication Provider

Setting up Auth0 as an 8base Authentication Provider