-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SCIM] Notification payload size too big #797
Comments
Hello, There are two possible solutions to address your issue. The first solution involves storing the content of the message in Blob storage and adding a reference to it within the message. The second solution is to split the message into chunks. KR, |
Ok, after few investigation on our side, I think that the best approach is to implement first solution, I mean store message to blob storage, if possible with a setting to enable or disable it. Can you please make this change? Thanks a lot. |
We will add this feature in the next release. KR, SID |
I made some modifications to the Release503 branch to support your scenario.
Changes : 54084df |
Nice, I will try it soon |
Hello , We tested the changes and all seems fine. Do you already have the plan for the release of the new version ? Regards |
A pre-release package, version 5.0.3-rc1, has been published and is available for use. |
Hello guys,
we have an issue with group notification.
We use Azure Service Bus, and it has (in standard tier) only 256kb payload limitation.
In our system we have a group with multiple users and when we add new user the notification of group payload exceeds 256kb.
Do you have a "workaround" for this issue? Or do we need to use Premium Azure Service Bus? That supports 100mb payload size?
Thanks
The text was updated successfully, but these errors were encountered: