Mateusz Mandera

Results 30 issues of Mateusz Mandera

As mentioned in https://github.com/onelogin/python-saml/issues/269, the default signatureAlgorithm used for signing SAMLRequests is `rsa-sha1`. With SHA1 being insecure, that's clearly not ideal (and may cause issues with certain providers who may...

Similarly to the equivalent issue for the mobile app (https://github.com/zulip/zulip-mobile/issues/3195), we might want to implement support for Client Certificates in the desktop app, to support deployments which may require them...

According to a user report, the icon stopped bouncing since 5.5.0. https://chat.zulip.org/#narrow/stream/16-desktop/topic/MacOS.20doc.20icon.20bounce.20expected.20behavior/near/1133801 is the relevant czo discussion #510 is the original feature request, but it seems more appropriate for me...

Fixes https://github.com/zulip/zulip/issues/22821. As explained in the comment in the code: Topics can be large enough that this request will inevitably time out. In such a case, it's good for some...

question
area: message-editing
size: M
integration review

Previously this was only available on the upgrade page - meaning an organization that already bought a plan wouldn't be able to request a sponsorship to get a discount or...

size: XL
has conflicts

As discussed around https://chat.zulip.org/#narrow/stream/31-production-help/topic/Message.20retention/near/1389970

size: S
integration review

The inverse of do_deactivate_remote_server. It's just flipping the .deactivated flag, but we also should have an AuditLog for these events.

size: M

Just like deactivated realms should be excluded, so should locally deleted realms. In particular, failure to exclude locally deleted realms breaks handle_customer_migration_from_server_to_realms.

size: XS

Only affects zulipchat, by being based on the BILLING_ENABLED setting. The restricted backends in this commit are - AzureAD - restricted to Standard plan - SAML - restricted to Plus...

area: authentication
size: XL
area: billing
integration review

Our social auth error handling used to completely not account for ``SOCIAL_AUTH_SUBDOMAIN``, leading to the user getting stuck on the auth subdomain, which could be confusing. I talked more about...

bug
area: authentication
size: XL
has conflicts
post release