I’m having trouble authenticating with the Go Jira command line interface. When I run jira login in my terminal, it prompts me for credentials but I keep getting errors.
Here’s what I’m doing:
jira login
When I enter my personal access token or regular password, I get this error message:
ERROR Post "rest/auth/1/session": unsupported protocol scheme ""
My setup uses SSO authentication and I haven’t created a config.yml file in the jira.d directory yet. I’m wondering if that’s part of the problem or if there’s something else I’m missing with the authentication process. Has anyone encountered this protocol scheme error before when setting up the go-jira client?
for sure! sounds like you’re not pointing to the right jira instance. had the same error too, just make that ~/.jira.d/config.yml file and add the correct endpoint. go-jira needs that to authenticate properly. hope this helps!
That protocol scheme error means your endpoint URL isn’t set up right. You said you don’t have a config.yml file - that’s exactly the problem. Go-jira needs to know your JIRA instance URL before it can authenticate. Create the config file at ~/.jira.d/config.yml and add your endpoint. For SSO setups, throw in the authentication method too. I ran into the same thing when setting up go-jira with our corporate instance. The tool has no clue where to send the auth request without proper endpoint config. Set up the config file first, then try logging in again.
The empty protocol scheme error happens when go-jira can’t find your JIRA server URL config. Since you’re using SSO, you’ll need to do an extra step. Create your config.yml file with the proper endpoint, then use a personal access token instead of your regular password - SSO environments need this. Generate the token from your JIRA account settings under security. Make sure your endpoint URL includes the full protocol like https://your-instance.atlassian.net, not just the domain. Once you’ve got both the endpoint configured and the right token, authentication should work. I’ve seen this exact issue tons of times with SSO setups where people skip the config file step.