diff options
| author | Tomas Bzatek <tbzatek@redhat.com> | 2014-05-14 16:14:40 +0200 |
|---|---|---|
| committer | Tomas Bzatek <tbzatek@redhat.com> | 2014-05-15 16:09:14 +0200 |
| commit | 086f5b87aa6ac3ea3cacf4e81903c6851a02f32d (patch) | |
| tree | 889521e72887abe9710e4d1a2e9931a1d84cbb96 /src/fan/CMakeLists.txt | |
| parent | 09c52ea4b5d3f94bd20dec9baafcdbc05b87f9e8 (diff) | |
| download | openlmi-providers-086f5b87aa6ac3ea3cacf4e81903c6851a02f32d.tar.gz openlmi-providers-086f5b87aa6ac3ea3cacf4e81903c6851a02f32d.tar.xz openlmi-providers-086f5b87aa6ac3ea3cacf4e81903c6851a02f32d.zip | |
account: Don't expose the LMI_Account.UserPassword value
According to the Simple Identity Management Profile (DSP1034)
document the LMI_Account.UserPassword property should not contain
the password itself, no matter how encrypted it is. It should either
contain an array of zero elements when password has been set or
NULL when password is missing or not configured.
Another change this commit brings is a more precise behaviour
of LMI_Account.ModifyInstance() method. When the UserPassword
property is array of zero elements, no change regarding password
is made. This case was previously treated as a request for password
removal. The DSP1034 profile doesn't specify such scenario, let's
treat it the same way as the GetInstance() operation.
Diffstat (limited to 'src/fan/CMakeLists.txt')
0 files changed, 0 insertions, 0 deletions