Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Codar1.80

Change Codar out-of-the-box user accounts for Windows and Linux

Codar ships with built-in user accounts. The user accounts are used to authenticate REST API calls and for initial setup and experimentation with the product. For security reasons, you may want to disable or change the passwords associated with these accounts (do not change the user names).

Note Do not create users in your LDAP directory that match the out-of-the-box users provided by Codar (the out-of-the-box users are admin, csaInboundUser, csaCatalogAggregationTransportUser, csaReportingUser, csaTransportUser, idmTransportUser, ooInboundUser, and codarintegrationUser). Creating the same users in LDAP may allow the out-of-the-box users unintended access to the Codar Console or give the LDAP users unintended privileges.

Codar Console user accounts

The following users ship out-of-the-box and are used with the Codar Console:

admin User: Codar Console
Username	admin
Default Password	cloud
Default Role	ROLE_REST
Usage	This account is used to initially log in to the Codar Console to configure the provider organization.
To Disable	Edit the `CSA_HOME\jboss‑as\standalone\ deployments\idm-service.war\WEB-INF\classes\csa-provider-users.properties` file. Update the `admin` property to disable this user account. For example, set `admin` to the following value (this value should be encrypted): `cloud,ROLE_REST,disabled` Note This property not only determines if the account is enabled, it also contains the password and the roles that control access to Codar. By default, the unencrypted value of this property is: `cloud,ROLE_REST,enabled` See Encrypt password for instructions). The encrypted value is preceded by `ENC` without any separating spaces and is enclosed in parentheses. Ensure there is no blank space at the end of the value.
To Change Password	If you change the password to this account, you must update the value of the password in the `csa-provider-users.properties` file and the `securityAdminPassword` property in the `csa.properties` file (you must use the same password). You must also update and use the same password for every REST API call that uses the password. Updating the admin property in csa-provider-users.properties Edit the `CSA_HOME\jboss-as\standalone\deployments\ idm-service.war\WEB-INF\classes\csa-provider-users.properties` file. Update the password portion of the `admin` value and encrypt the entire value, including the roles and account status (see Encrypt password). An encrypted password is preceded by `ENC` without any separating spaces and is enclosed in parentheses. Ensure there is no blank space at the end of the value. Note This property not only contains the password, but also the roles that control access to Codar and if the account is enabled. By default, the unencrypted value of this property is: `cloud,ROLE_REST,enabled` Updating the securityAdminPassword property in csa.properties Edit the `CSA_HOME\jboss‑as\standalone\ deployments\csa.war\WEB-INF\classes\csa.properties` file and update the value of the `securityAdminPassword` property. Use the same encrypted password that you entered for the `admin` property in the `csa-provider-users.properties` file. After modifying the `csa.properties` file, restart Codar, see Restart Codar .

idmTransportUser User: Codar Console
Username	idmTransportUser
Default Password	idmTransportUser
Default Roles	ROLE_AMIN, PERM_IMPERSONATE
Usage	This account is used to authenticate REST API calls.
To Disable	Do not disable this account.
To Change Password	If you change the password to this account, you must update the value of the `securityIdmTransportUserPassword` property in the `csa.properties` file and the `idmTransportUser` property in the `integrationusers.properties` file (you must use the same password) and you must clear the JBoss server and web browser caches. You must also update and use the same password for every REST API call that uses the password. Updating the securityIdmTransportUserPassword property in csa.properties Edit the `CSA_HOME\jboss‑as\standalone\ deployments\csa.war\WEB-INF\classes\csa.properties` file and update the value of the `securityIdmTransportUserPassword` property. Determine a suitable new password (see Encrypt password). An encrypted password is preceded by `ENC` without any separating spaces and is enclosed in parentheses. Ensure there is no blank space at the end of the value. Updating the idmTransportUser property in integrationusers.properties Note This property not only contains the password, but also the roles that control access to Codar and if the account is enabled. By default, the unencrypted value of this property is: `idmTransportUser,ROLE_ADMIN,PERM_IMPERSONATE,enabled` Edit the `CSA_HOME\jboss-as\standalone\deployments\ idm-service.war\WEB-INF\classes\integrationusers.properties` file and update the value of the `idmTransportUser` property. Use the same password that you used for the `securityIdmTransportUserPassword` property in the `csa.properties` file and encrypt the entire value of the `idmTransportUser` property, including the roles and account status (see Encrypt password). An encrypted password is preceded by `ENC` without any separating spaces and is enclosed in parentheses. . Ensure there is no blank space at the end of the value.
	Clearing the JBoss server and web browser caches After modifying and saving the changes to the files, clear the JBoss server and web browser caches. To clear the JBoss server cache, remove the contents from the `CSA_HOME\jboss-as\standalone\tmp` directory. See Clear web browser cache for information on how to clear the web browser cache. Restarting Codar After making these changes, restart Codar, see Restart Codar.

ooInboundUser User: Codar Console
Username	ooInboundUser
Default Password	cloud
Default Role	ROLE_REST
Usage	This account is used by Operations Orchestration to authenticate REST API calls with Codar.
To Disable	Do not disable this account.
To Change Password	If you change the password to this account, you must update the value of the password in the `csa-provider-users.properties` file and the `securityOoInboundUserPassword` property in the `csa.properties` file (you must use the same password). You must also update and use the same password for every REST API call that uses the password. Updating the ooInboundUser property in csa-provider-users.properties Edit the `CSA_HOME\jboss-as\standalone\deployments\ idm-service.war\WEB-INF\classes\csa-provider-users.properties` file. Update the password portion of the `ooInboundUser` value and encrypt the entire value, including the roles and account status (see Encrypt password for instructions on how to encrypt this value). The encrypted value is preceded by `ENC` without any separating spaces and is enclosed in parentheses. Ensure there is no blank space at the end of the value. Note This property not only contains the password, but also the roles that control access to Codar and if the account is enabled. By default, the unencrypted value of this property is: `cloud,ROLE_REST,enabled` You must also update and use the same password for the `CSA_REST_CREDENTIALS` system account in Operations Orchestration (located in the Configuration folder of the Public Repository). Updating the securityOoInboundUserPassword property in csa.properties If you change the password to this account, you must update the value of the `securityOoInboundUserPassword` property in `csa.properties`. You must also update and use the same password for the `CSA_REST_CREDENTIALS` system account in Operations Orchestration (located in the Configuration folder of the Public Repository). Edit the `CSA_HOME\jboss‑as\standalone\ deployments\csa.war\WEB-INF\classes\csa.properties` file and update the value of the `securityOoInboundUserPassword` property. Use the same encrypted password that you entered for the `ooInboundUser` property in the `csa-provider-users.properties` file. After modifying the `csa.properties` file, restart Codar, see Restart Codar .

codarintegrationUser: Codar Console
Username	codarintegrationUser
Default Password	cloud
Default Role	codarintegrationUser
Usage	This account is used in the Jenkins plug-in for integrating with Codar.
To Disable	It is recommended to enable this account so that Jenkins integration will work.
To Change Password	If you change the password to this account, you must update the value of the password in the `csa-provider-users.properties` file and the `securitycodarintegrationUserPassword` property in the `csa.properties` file (you must use the same password). You must also update and use the same password for every REST API call that uses the password. Updating the codarintegrationUser property in csa-provider-users.properties Edit the `CSA_HOME\jboss-as\standalone\deployments\ idm-service.war\WEB-INF\classes\csa-provider-users.properties` file. Update the password portion of the `codarintegrationUser` value and encrypt the entire value, including the roles and account status (see Encrypt password). An encrypted password is preceded by `ENC` without any separating spaces and is enclosed in parentheses. Ensure there is no blank space at the end of the value. Note This property not only contains the password, but also the roles that control access to Codar and if the account is enabled. By default, the unencrypted value of this property is: `cloud,ROLE_REST,enabled`. You must also update and use the same password for the `CSA_REST_CREDENTIALS` system account in Operations Orchestration (located in the Configuration folder of the Public Repository). Updating the securitycodarintegrationUserPassword property in csa.properties If you change the password to this account, you must update the value of the `securitycodarintegrationUserPassword` property in `csa.properties`. You must also update and use the same password in `CSA_REST_CREDENTIALS` system account in Operations Orchestration (located in the Configuration folder of the Public Repository). Edit the `CSA_HOME\jboss‑as\standalone\ deployments\csa.war\WEB-INF\classes\csa.properties` file and update the value of the `securitycodarintegrationUserPassword` property. Use the same encrypted password that you entered for the `codarintegrationUser` property in the `csa-provider-users.properties` file. After modifying the `csa.properties` file, restart Codar, see Restart Codar .

Note: The codarintegrationUser user account is for the purpose of integrating Codar with external interfaces such as Jenkins. It is highly recommended that you manage this account in LDAP and to do this you need to add this user account to LDAP. For more details, see Prepare LDAP for CodarE.

Send Help Center feedback