The following examples show the requests and responses that are defined in the XSD files for the UpdateSysAdminUser tag.
This request follows the UpdateSysAdminUser tag defined in the XSD files.
<XmlInterfaceRequest>
<UpdateSysAdminUser>
<SysAdminUser>
<Name>admin1</Name>
<Description>New The default administrator user with all
privileges</Description>
<LockedStatus>0</LockedStatus>
<RoleRef>
<Name>Administrator</Name>
</RoleRef>
<ScopeRef>
<Name>Global</Name>
</ScopeRef>
</SysAdminUser>
</UpdateSysAdminUser>
</XmlInterfaceRequest>
250 characters (string); can only contain the characters A–Z, a–z, 0–9, period (.), hyphen (-), and underline (_).
250 characters (string)
A clear text
0 = unlocked; 1 = locked
Can specify only one role
Can specify multiple scopes
Specified User does not exist: '{$UserName}'
The specified user is not in system.
Invalid User Name for: '{$UserName}'
User Name is an empty string.
User Name exceeds max length for: '{$UserName}'
UserName exceeds max length (250 characters).
User Description exceeds max length. User: '{$UserName}'
Description exceeds max length (250 characters)
User: '{$Username}' must have an associated Role and Scope.
Non-Role or non-Scope is defined in OSSI command.
Invalid Role Name for: '{$RoleName}'
RoleName exceeds max length (250 characters), or There is more than one Role defined.
Invalid Scope Name for: '{$ScopeName}'
ScopeName exceeds max length (250 characters).
The user: {$UserName}'s associated role does not exist. Please create it first.
RoleName is an empty string, or RoleName is not defined in CMP.
The user: {$UserName}'s associated scope does not exist. Please create it first.
ScopeName is an empty string, or ScopeName is not defined in CMP.
If the input OSSI command cannot match the schema specification, thereis an error-message response to the operator. For example, if you define a LockStatus with a string, the following message is reported:
Error parsing import file: Error parsing import file: cvc-datatype-valid.1.2.1: 'ABC' is not a valid value for 'integer'.
The response to this request follows the generic Response tag defined in the XSD files.
<Response> <Result>0</Result> <Command type="XmlInterfaceResponse"> <Success count="1">Successfully updated 1 User(s).</Success> <Failure count="0"></Failure> </Command> </Response>
This request follows the UpdateSysAdminUser tag defined in the XSD files.
<XmlInterfaceRequest>
<UpdateSysAdminUser>
<SysAdminUser>
<Name>NotExistadmin1</Name>
<Description>New The default administrator user with all
privileges</Description>
<LockedStatus>0</LockedStatus>
<RoleRef>
<Name>Administrator</Name>
</RoleRef>
<ScopeRef>
<Name>Global</Name>
</ScopeRef>
</SysAdminUser>
</UpdateSysAdminUser>
</XmlInterfaceRequest>
The following error response occurs when the user name does not exist.
<Response> <Result>0</Result> <Command type="XmlInterfaceResponse"> <Success count="0"></Success> <Failure count="1">Failed to update 1 User(s). Specified User does not exist: "NotExistadmin1"</Failure> </Command> </Response>
This request follows the UpdateSysAdminUser tag defined in the XSD files.
<XmlInterfaceRequest>
<UpdateSysAdminUser>
<SysAdminUser>
<Name>admin1</Name>
<Description>New The default administrator user with all
privileges</Description>
<LockedStatus>0</LockedStatus>
<RoleRef>
<Name>not exist Administrator</Name>
</RoleRef>
<ScopeRef>
<Name>Global</Name>
</ScopeRef>
</SysAdminUser>
</UpdateSysAdminUser>
</XmlInterfaceRequest>
The following error response occurs when the role specified for the user does not exist.
<Response> <Result>0</Result> <Command type="XmlInterfaceResponse"> <Success count="0"></Success> <Failure count="1">Failed to update 1 User(s). The user: admin1's associated role does not exist. Please create it first.</Failure> </Command> </Response>
This request follows the UpdateSysAdminUser tag defined in the XSD files.
<XmlInterfaceRequest>
<UpdateSysAdminUser>
<SysAdminUser>
<Name>admin1</Name>
<Description>New The default administrator user with all
privileges</Description>
<LockedStatus>0</LockedStatus>
<RoleRef>
<Name>Administrator</Name>
</RoleRef>
<ScopeRef>
<Name>Not exist Global</Name>
</ScopeRef>
</SysAdminUser>
</UpdateSysAdminUser>
</XmlInterfaceRequest>
The following error response occurs when the specified scope does not exist for the user.
<Response> <Result>0</Result> <Command type="XmlInterfaceResponse"> <Success count="0"></Success> <Failure count="1">Failed to update 1 User(s). The user: admin1's associated scope does not exist. Please create it first.</Failure> </Command> </Response>
This request follows the UpdateSysAdminUser tag defined in the XSD files.
<XmlInterfaceRequest>
<UpdateSysAdminUser>
<SysAdminUser>
<Name>admin1</Name>
<Description>New The default administrator user with all
privileges</Description>
<LockedStatus>0</LockedStatus>
<RoleRef>
<Name>123</Name>
</RoleRef>
<RoleRef>
<Name>Administrator</Name>
</RoleRef>
<ScopeRef>
<Name>123</Name>
</ScopeRef>
</SysAdminUser>
</UpdateSysAdminUser>
</XmlInterfaceRequest>
The following error response occurs when the role name either exceeds the maximum length of 250 characters, or there is more than one Role defined.
<Response> <Result>0</Result> <Command type="XmlInterfaceResponse"> <Success count="0"></Success> <Failure count="1">Failed to update 1 User(s). Invalid Role Name for: "admin1"</Failure> </Command> </Response>