-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identify session invalidity #196
Comments
You might want to use a tool like Maybe you can use |
The first sentence would be a solution.. The second is exactly what I like to prevent cause if someone runs a script which contains a command like Maybe it would be possible having a return code saying you are not logged in anymore you have to use Maybe I misunderstand a thing...at the moment...nevertheless thanks for your answer... |
Okay, this sort of functionality seems to be getting harder with Jira. They are moving away from the cookie based sessions and moving towards requiring basic auth for every request, at least they have dropped support for session based authentication on hosted atlassian.net services. I assume you are using a locally hosted jira that still supports the |
Added |
Wow ...great...I will try within the next days..Thanks for your support.. |
Overview
Lets say I've worked a time with the command line client and than make a break ..
afterwards I use another command and I'm prompted with the password input...
Suggestion
It would be great having a command which tell me that the session has expired and I need to do relogin (type i my password). This would be great for scripting to show the user an explicit message "you have to login".
this would prevent scripts from eating up the
password dialog
(? Jira Password [username]:
)if the output has been redirected...Idea
go-jira session
return code:
Another idea would be to have an explicit return code in each command could tell me the same.
BTW: Really great tool very helpful.
The text was updated successfully, but these errors were encountered: