Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
MacOS Error when signing SAML Response

Hello,

When we use the Q2SamlResponse class and run the sign function with our cert on a Mac computer, we get the following error:

q2_sdk.models.saml_response.MacOSError: A recent update to MacOS has issues with the xmlsec library

We tried updating that package, reinstalling it, everything but still get the issue.

We are using SDK v2.266.1

Votes Newest

Answers


Unfortunately, it's more complicated than that. xmlsec itself depends on libxmlsec1, which is a C library. These can either be compiled to order or pulled as precompiled wheel (whl) files for python based on each operating system.

On Friday, I uploaded precompiled wheels for all the mac + xmlsec + lxml versions I had access to and reuploaded them. Even so, there's is a segfault potential in the xmlsec package on modern mac versions. As such, since 2.266.1, rather than segfaulting, we try multiple times in a subprocess to sign the XML, then if after 10 tries it never works we throw this error.

I recommend pip uninstall xmlsec, then pip install xmlsec --no-cache as your best bet. If you have an alternative that involves a less segfaulty solution on Mac, I'm all ears. This particular bug has been quite the frustrating one on the internet boards.

Posted one year ago
Brian Mego
227 × 1 Administrator
129 Views
1 Answer
one year ago
one year ago
Tags