Skip to content

jira init fails due to company middleware #1025

Description

@maritaria

Describe the bug
I'm trying to set up jira-cli (jira init) using type Local > Bearer. Once I enter my email, jira-cli crashes with output:

~ # jira init
? Installation type: Local
? Authentication type: bearer
? Link to Jira server: https://${sub_domain}.${company}.com/
? Login username: ${my_email}

✗ Unable to generate configuration: invalid character '<' looking for beginning of value

My company has a self-hosted JIRA instance and also adds middleware to enable SSO and integrate it into the wider "digital landscape" of the org. So my guess is that jira-cli tries to fetch some info from the instance but hits a general "you are not logged in" redirector page, because it doesn't have my tokens yet.

Our instance does work once you are on the right VPN and access it with a PAT.

Please provide following details

  1. JiraCLI Version:
    (Version="v1.7.0", GitCommit="79067e2422df10e59f310bd6fd4979f43a1df0e7", CommitDate="2025-08-30T08:30:25+00:00", GoVersion="go1.24.6", Compiler="gc", Platform="linux/arm64")
    
  2. Are you using Jira cloud or on-premise jira server?
    ~ # jira serverinfo
    

The tool needs a Jira API token to function.

For cloud server: you can generate the token using this link: https://id.atlassian.com/manage-profile/security/api-tokens
For local server: you can use the password you use to log in to Jira for basic auth or get a token from your Jira profile for PAT.

After generating the token, you can either:

  • Export API token to your shell as a JIRA_API_TOKEN env variable
  • Or, you can use a .netrc file to define required machine details

Once you are done with the above steps, run 'jira init' to generate the config if you haven't already.

For more details, see: https://github.com/ankitpokhrel/jira-cli#getting-started
3. What operating system are you using? Also mention version.
MacOS, but I'm running through docker.
4. What terminal are you using? Also mention version.
Ghostty, but I'm running through docker.
```

To Reproduce

Steps to reproduce the behavior:
1.
2. ...
3. See error

Expected behavior

Screenshots

Additional context

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions