User 2.5 Update
This topic describes how to update metadata, grant/revoke user groups and user roles to existing Content Manager users or user profiles.
Parameters
| Name | Type | Direction | Description |
|---|---|---|---|
| psAuthContext | String | InOut | Deprecated proprietary authentication context only used by .ASMX web services based on internal username/password authentication. Claims based security standards drive all the WCF .SVC web services making this parameter redundant. |
| psUserId | String | In | The element name of the user (e.g. VUSERADMIN) |
| psXMLMetaData | String | In | Metadata XML structure with the metadata that will be set on the current object |
Requirements are:
- Only an Administrator user can update metadata of all users.
- You have to be an Administrator user to update security fields such as:
FUSERGROUPFISHUSERROLESFISHUSERTYPEPASSWORDFISHOBJECTACTIVEFISHUSERDISABLED- ...
- Except security fields, each user can update the properties (e.g. USERNAME, FISHEMAIL) of its own account.
Note that:
- The
levelattribute on theishfieldelement must be 'none'. - In order to rename the user you have to add the field
USERNAMEwith the new user name topsXMLMetaData. - To deactivate the user, add the following statement to
psXMLMetaData<ishfield name='FISHOBJECTACTIVE' level='none' ishvaluetype='element'>FALSE</ishfield> -
To disable the user, add the following statement to
psXMLMetaData<ishfield name='FISHUSERDISABLED' level='none' ishvaluetype='element'>TRUE</ishfield> - When supplying the field
PASSWORD, make sure the password is compliant with the Content Manager password complexity rules - When changing the user type from
InternaltoExternal, you have to set theFISHEXTERNALIDfield. ThePASSWORDfield is kept but is no longer used. - When changing the user type from
ExternaltoInternal, you must supply thePASSWORD.