EDIT_GROUP EDIT_ROLE EDIT_USER

4-140 Oracle Fusion Middleware Services Reference Guide for Oracle Universal Content Management ClientEncoding=Cp1252 dUser=sysadmin blDateFormat=Md{yy} {h:mm[:ss] {aa}[zzz]}tAmericaChicagomAM,PM monitoredSubjects=usermetaoptlists,1008541017549,aliases,1008541017549, userlist,1008541017549,users,1008541017549,metadata,1008541017549,config, 1008541017549,accounts,1008541017549 loadedUserAttributes=1 dUserName=sysadmin watchedMonikers= IdcService=EDIT_ALIAS blFieldTypes=StatusMessage message changedMonikers= dAliasDescription=Test Alias changedSubjects= monitoredTopics=appcommongui,1000382277000 end ResultSet AliasUserMap 2 dAlias 6 30 dUserName 6 50 YourAlias Gillian YourAlias Monique YourAlias sysadmin end ResultSet UpdatedUserTopics 3 topicName topicValue topicTS end ResultSet Alias 2 dAlias 6 30 dAliasDescription 6 50 MyAlias This is a test of adding an alias NewAlias Test Alias YourAlias Test Alias end

4.14.12 EDIT_GROUP

Service that modifies an existing security group. Location: IdcHomeDirresourcescoretemplatesstd_services.htm Additional Required Service Parameters ■ dGroupName: The security group name. ■ dDescription: The security group description. ■ dPrivilege: The permission setting. If this value is set to 0, only the admin role has RWDA permission on the group. No other roles are able to access the group. If the value is set to 15, all roles get RWDA permission on the group. Core Oracle Content Server Services 4-141 Example IdcService=EDIT_GROUP dGroupName=MY_GROUP dPrivilege=0 dDescription=admin privileges

4.14.13 EDIT_ROLE

Service that modifies an existing role. A role is a set of permissions Read, Write, Delete, Admin for each security group. Location: IdcHomeDirresourcescoretemplatesstd_services.htm Additional Required Service Parameters ■ dRoleName: The existing role name. ■ dGroupName: The name of the security group. Optional Service Parameters ■ dPrivilege: The permission setting. If this value is set to 0, only the admin role has RWDA permission on the group. No other roles are able to access the group. If the value is set to 15, all roles get RWDA permission on the group. For more information about numbering of permissions, see Oracle Fusion Middleware System Administrators Guide for Oracle Content Server. Example IdcService=EDIT_ROLE dRoleName=test_role dGroupName=MY_GROUP dPrivilege=15

4.14.14 EDIT_USER

Service that modifies an existing user. The most likely error is the user not having the security level to perform this action or the user not existing. Location: IdcHomeDirresourcescoretemplatesstd_services.htm Additional Required Service Parameters ■ dName: The user name. ■ dUserAuthType: The user authorization type. This value must be set to either Local or Global. Caution: Editing a user deletes all existing user attributes role and account permissions. To retain existing attributes, you must include the existing attributes along with any new or changed data. If user attributes are not defined, the user belongs to no roles or accounts, and becomes a guest in the system. Note: If the specified user does not exist, the Oracle Content Server system adds the user. 4-142 Oracle Fusion Middleware Services Reference Guide for Oracle Universal Content Management Optional Service Parameters ■ dFullName: The full name of the user. ■ dPassword: The password for the user. ■ dEmail: The email address of the user. ■ dUserLocale: The locale designation, such as English-US, English-UK, Deutsche, Français, or Español. ■ dUserType: The user type. Optional Attribute Information Optional attributes are specified as a result set that contains the users attribute information and specifies the roles the user belongs to and the accounts the user has access to. Attribute information consists of a list of three comma-delimited strings. The first string indicates the type of attribute, the second the name of the attribute, and the third is the access number for accounts or default entry for role. ■ Attribute Type: When defining a role, the first string specifies that this is a role attribute, the second string is the name of the role, and the third is the default entry of 15. When defining an account, the first string specifies that this is an account attribute, the second string is the name of the account, and the third is the access level. – For a role attribute, the information is in the form: role,contributor,15 – For an account attribute, the information is in the form: account,books,1 ■ Attribute Name: A user can belong to multiple roles and accounts, so there can be multiple role and account information strings separated by commas in the attribute information column. If the user is to have the admin role, define the user attribute information as follows: ResultSet UserAttribInfo 2 dUserName AttributeInfo jsmith role,contributor,15 end If the user is to belong to both the contributor and editor roles and have Read permission on the books account, define the user attribute information as: ResultSet UserAttribInfo 2 dUserName AttributeInfo jsmith role,contributor,15,role,editor,15,account,books,1 end Core Oracle Content Server Services 4-143 ■ Access Number: These access numbers can be assigned to the user. – 1: Read only – 3: Read and write – 7: Read, write, delete – 15: Administrative permissions Example ■ IdcCommand command file format: IdcService=EDIT_USER dName=user20 dUserAuthType=Local ■ HDA format with optional parameters and attribute information: Properties LocalData IdcService=EDIT_USER dName=jsmith dFullName=Jennifer Smith dUserAuthType=Local dPassword=password dEmail=jsmithexample.com dUserType=MKT dUserLocale=English-US end ResultSet UserAttribInfo 2 dUserName AttributeInfo jsmith role,admin,15,role,contributor,15 end

4.14.15 EDIT_USER_PROFILE