Support new fdo secrets API property names
Bug #800294 reported by
dobey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Ubuntu Single Sign On Client | Status tracked in Trunk | |||||
Trunk |
Fix Released
|
High
|
dobey | |||
ubuntu-sso-client (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | |||
Bug Description
Along with a couple of API signatures in the FDo secrets API being changed in gnome-keyring 3.x, some of the property names on various types also changed. We need to support these in a manner that allows us to fall back, and work with both versions of gnome-keyring.
Related branches
lp:~dobey/ubuntu-sso-client/new-kr-props
- Alejandro J. Cura (community): Approve
- Natalia Bidart (community): Approve
-
Diff: 220 lines (+79/-23)2 files modifiedubuntu_sso/utils/tests/test_txsecrets.py (+27/-5)
ubuntu_sso/utils/txsecrets.py (+52/-18)
Changed in ubuntu-sso-client (Ubuntu): | |
milestone: | none → oneiric-alpha-2 |
To post a comment you must log in.
This bug was fixed in the package ubuntu-sso-client - 1.3.1-0ubuntu1
---------------
ubuntu-sso-client (1.3.1-0ubuntu1) oneiric; urgency=low
* New upstream release.
- Invalid signature for CreateItem call (LP: #745540)
- Never sees NetworkManager connection (LP: #791548)
- Support new property names in secrets API (LP: #800294)
- Deprecated DBus interfaces not marked as such (LP: #770269)
* Update the watch file to point at the correct place.
-- Rodney Dawes <email address hidden> Fri, 24 Jun 2011 15:14:18 -0400