Bug 1244512
| Summary: | Api call user.getLoggedInTime returns un-timestamped value. | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Matej Kollar <mkollar> |
| Component: | API | Assignee: | Jan Dobes <jdobes> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.3 | CC: | cperry, jdostal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-11 13:07:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1484117 | ||
user.getLoggedInTime has been already deprecated. Closing this one. This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug. |
Description of problem: Timestamp value returned by user.getLoggedInTime is not timestamped and thus is useless. Version-Release number of selected component (if applicable): How reproducible: allways/deterministic Steps to Reproduce: 1. Run the following script parametrized by hostname of your Spacewalk: #!/usr/bin/env python import xmlrpclib import sys USER = "admin" PASS = "nimda" SERVER = "http://%s/rpc/api" % sys.argv[1] client = xmlrpclib.Server(SERVER, verbose=0) client2 = xmlrpclib.Server(SERVER, verbose=1) key = client.auth.login(USER, PASS) client2.user.getLoggedInTime(key, "admin") client.auth.logout(key) Actual results: Response body contains something like <dateTime.iso8601>20150719T09:54:46</dateTime.iso8601> (Which in case you are not in the same timezone as a server, is not exactly useful.) Expected results: Timezoned value Additional info: * ISO 8601 allows use of timezone * possible workaround is using user.getDetails which return struct with field last_login_date. That is string formatted in the following way: user never logged in: "" otherwise: example "7/3/15 4:41:06 AM EDT" (that is not a ISO 8601 but might be parsable just ok) * Why not deprecate user.getLoggedInTime?