Skip to content
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

cisco_imc_login doesn't return anything other than successful login. #7

Open
sandinak opened this issue Feb 17, 2017 · 1 comment
Open

Comments

@sandinak
Copy link
Contributor

Just did a bit of research on this for my needs:

  • assuming you use the cisco_imc_login .. you'd want at least a cookie passed back to use on subsequent calls
  • right the server handle which is returned is not serializable in JSON.. the cookie would be
  • IMCSDK has not facilities in imchandle for this.. tho we should be able to pass the cookie and validtate it's usable if we get it.. and refresh.
@vvb
Copy link
Member

vvb commented Feb 19, 2017

@sandinak The idea is to return a serialised ImcHandle object back.. so that other tasks will be able to de-serialise it and use.

Just returning cookie from it, makes it much harder for the cookie to be used. Not to mention, that there are instances where the server can refresh the cookie value and the one we return from cisco_imc_login may not be valid after a certain time. And so, having the entire handle object is critical as it has information that can be used to re-login in cases when the cookie has gone stale.

This case has been thought out. Will check to see if the implementation is in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants