-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Authentication System : DISABLED #299
Comments
Running (qgis_ltr) ➜ qgis-feedstock git:(osx_arm64_native) qcatool-qt5 plugins --debug |
So I have create a empty environment and installed qca and I don't get any problems with the plugin (qca_test) ➜ qgis-feedstock git:(osx_arm64_native) qcatool-qt5 plugins --debug So it must be something on QGIS recipe. @gillins any ideas? |
@conda-forge/openssl Team any ideas? QCA openssl plugin is complaining
|
That's the problem. It seems to be looking for If qgis has no OpenSSL 3 support (yet), then that's an issue, because conda-forge recently moved to OpenSSL 3 only. If so, you can pin to OpenSSL 1.1.1 in the host deps, but that's not a long-term solution, as it will become uninstallable with many other conda-forge packages (and OpenSSL 1.1.1 is EOL in September). |
Looking at my normal Linux installation, it seems that my linux machine uses openssl 3.0.2, and qgis uses it fine. So it means that is something on our recipe. Nevertheless, forcing openssl =1.1.1 seems to fix the problem as @h-vetinari suggested. But we probably should try a better fix. |
Is that one installed through conda-forge or some other way? It may be picking up some other openssl lying around on the path, because if it's looking for |
No, this one was installed from apt and qgis 3.28.3 also installed from apt works fine. Which means QGIS supports openssl 3. So something is up with our recipe or environment. |
Need to see if there are any symbolic links to fake the 1.1.1 file |
This shouldn't be changed by deleting/modifying symlinks. You need to check the upstream build configuration/options how to tell it to use OpenSSL 3. |
Sorry @SrNetoChan , just catching up with this. So this is fine on Linux, right? I just checked there and seems ok, but unfortunately I don't have access to OSX anymore so can't easily compare. |
@gillins no, I am getting this on Linux too. So at least OSX and Linux, haven't tried Windows |
That's weird because on my system |
What is your Linux machine? Mine is kubuntu 22.04. I saw something about a similar error only appearing in certain ubuntu versions. |
Ubuntu 22.04. Using QGIS 3.28.2. |
Ah! The problem only starts with 3.28.3 (the one I have merged yesterday or so). It happens both for the LTR and the Stable version. So, something seems to have changed. |
That could be. If the package depends on openssl, you need to declare it like that |
Weird, something did change in this migration: #293 - I had to add the winsock library on Windows in when I never had to do this before. Maybe something changed in the build images? |
So, I have tried to update my qgis LTR environment to 3.22.16 expecting it to fix the issue with OpenSS, but it didn't. Then I deleted that environment and started over and, surprise it worked! So a clean environment can make a difference. |
Also tried with QGIS 3.28.3 and it also worked. So what we did in the qca should have fixed the problem... I hope. |
I still have this problem with 3.34.1 in Mac m2 |
@wybert can you elaborate on your environment? |
@SrNetoChan I also tried 3.36.0 in mac m2, my conda env is like below,
|
Solution to issue cannot be found in the documentation.
Issue
I am getting this issue
2023-01-29T02:24:38 CRITICAL Authentication System : DISABLED. Resources authenticating via the system can not be accessed
This is new on 3.22.15 and 3.28.3 (tested while trying to build on a M1 machine)
I wonder if it has something to do with this old error:
qgis/QGIS#22615 (comment)
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: