jiralib2 queries API as anonymous user even after I login

[romariorios]

This is my setup:

(require 'use-package)
(use-package jiralib2
  :init
  (setq jiralib2-url jira-server
        jiralib2-auth 'basic
        jiralib2-user-login-name user
        request--curl-cookie-jar "")) ; following troubleshooting tip at README
                                      ; (it didn't work)

When I try to perform a query with jiralib2-jql-search, the following happens:

1. Jiralib asks me for my password
2. I get an error 400 and the following response from the API:

   user-error: Request failed: invalid request:
   ((errorMessages
   Field 'assignee' does not exist or this field cannot be viewed by anonymous users.
   Field 'issuetype' does not exist or this field cannot be viewed by anonymous users.)
   (errors))

My current workaround is switching back and forth from 'basic to 'cookie and running M-x jiralib2-session-login until the query works (it usually takes one back and forth).

Any idea of what's going on?

• OS: Debian 11
• M-x emacs-version: GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0) of 2021-03-27, modified by Debian -curl --version:

  curl 7.74.0 (x86_64-pc-linux-gnu) libcurl/7.74.0 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0) libssh2/1.9.0 nghttp2/1.43.0 librtmp/2.3
  Release-Date: 2020-12-09
  Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp 
  Features: alt-svc AsynchDNS brotli GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets

[romariorios]

Update: it seems leaving jiralib2-auth as 'cookie now works? Not sure if that has anything to do with the (setq request--curl-cookie-jar "") workaround.

I'll be back in a few days and close this issue if it keeps working.

[romariorios]

I think keeping the cookie authentication and setting request--curl-cookie-jar worked? I no longer have any authentication issues.

Closing this.