Hi, Since the 1.21 upgrade https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-e159fd578d
moshimoshi to our 1.19 server.
Traceback (most recent call last): File "/usr/bin/koji", line 335, in <module> rv = locals()[command].__call__(options, session, args) File "/usr/lib/python2.7/site-packages/koji_cli/commands.py", line 7389, in handle_moshimoshi activate_session(session, options) File "/usr/lib/python2.7/site-packages/koji_cli/lib.py", line 700, in activate_session session.gssapi_login(proxyuser=runas) File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2572, in gssapi_login raise AuthError('unable to obtain a session') koji.AuthError: unable to obtain a session
and server side
[Mon Apr 27 14:22:46.061394 2020] [:error] [pid 3673303] raise koji.AuthError('could not verify client: %s' % context.environ.get('SSL_CLIENT_VERIFY')) [Mon Apr 27 14:22:46.061397 2020] [:error] [pid 3673303] AuthError: could not verify client: NONE
Things were okay with the 1.20 client.
It looks, that gssapi is not enabled there? (in other words: REMOTE_USER is not populated by httpd)
Metadata Update from @tkopecek: - Custom field Size adjusted to None
We've deprecated old-style krbV login #1906
Old issue. As Tomas indicates, clients from 1.21 on can't perform the old krbV auth. Hubs since 1.11 or so should be able to support gssapi auth.
I'm going to close this. If you're still having trouble (and the hub in question does have gssapi configured), then reopen with more details.
Metadata Update from @mikem: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/2201
Please continue any further discussion there.