You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a webservice that allows me to open a session by authenticating with my agent username and password.
When I'm done with the service I would like to remove my session using the SessionRemove Operation.
I expect to be able to do that using only my Session ID and username.
Actual behavior
I get an authentication failure unless I also specify my agent password in the SessionRemove request.
90% of the reason I'm using a session is because I don't want to hold on to the user's password in my script and I don't see a reason why the password is required - at least to remove my own session, the Session ID should suffice as authentication, that's kind of its purpose, right?
How to reproduce
Steps to reproduce the behavior:
Create a WebService with at least the SessionCreate and SessionRemove operations
Create a session. I'm using python requests
Remove the session without specifying your password.
Additional information
Screenshots
The text was updated successfully, but these errors were encountered:
Environment
Expected behavior
I have a webservice that allows me to open a session by authenticating with my agent username and password.
When I'm done with the service I would like to remove my session using the SessionRemove Operation.
I expect to be able to do that using only my Session ID and username.
Actual behavior
I get an authentication failure unless I also specify my agent password in the SessionRemove request.
90% of the reason I'm using a session is because I don't want to hold on to the user's password in my script and I don't see a reason why the password is required - at least to remove my own session, the Session ID should suffice as authentication, that's kind of its purpose, right?
How to reproduce
Steps to reproduce the behavior:
Additional information
Screenshots
The text was updated successfully, but these errors were encountered: