Bug #839
Scheduler doesn't understand new auth. tokens
| Status: | Closed | Start date: | 09/28/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Scheduler | |||
| Target version: | Release 3.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 3.0 |
Description
Normal auth tokens, stored in ONE_AUTH or ~/.one/one_auth contain the string user:pass, which is read by the client and sent to the core as user:sha1(pass)
With the new authentication drivers, these tokens can be in the form user:driver:pass, and must be sent without any modification in the XML-RPC requests.
Associated revisions
Bug #839: Add support in scheduler for auth tokens with protocol
Bug #839: Add support in java oca for auth tokens with protocol
Bug #839: Add support in scheduler for auth tokens with protocol
(cherry picked from commit 2bb8ce1e88d0dc3a9a9eb9de2f9c3f81aec2b07b)
Bug #839: Add support in java oca for auth tokens with protocol
(cherry picked from commit 9ee34a8b87938d440d110cfb58f3c094302093e9)
Bug #839: Fix typo in java OCA Client.java
Bug #839: Fix typo in java OCA Client.java
(cherry picked from commit 7b2414e07705a1b8417bd9aa4828a0f49424a5fd)
History
#1
Updated by Carlos Martín almost 10 years ago
- Status changed from New to Closed
- Resolution set to fixed