When I upgraded Koji to version 1.35, I found that calling Koji's gssapi_login failed. The debug code is “sigul --batch sign-rpm --store-in-koji --koji-only ts4 tencent-audit-1.0.20-1.sel4.x86_64”
But I can use koji hello, and the koji.conf of the bridge configuration also configures no_ssl_verify = True, so I wonder if the new version of koji has changed the authentication of sigul's ssl
Metadata Update from @jiaxin: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)