1,126
edits
Difference between revisions of "arsstash"
Jump to navigation
Jump to search
m
A little more detail on the usage of the IBM CMOD arsstash command.
(Initial draft of IBM CMOD arsstash article.) |
m (A little more detail on the usage of the IBM CMOD arsstash command.) |
||
| Line 2: | Line 2: | ||
The IBM CMOD arsstash command allows for the storage of user credentials (User ID & Password) in an encrypted format, which meets many organizations requirement for storing authentication information securely (i.e., non-plain text files like shell scripts or files protected only by Operating Systems permissions). Stash files replace the arsload.cfg configuration file used in versions of IBM Content Manager OnDemand prior to V9.0. | The IBM CMOD arsstash command allows for the storage of user credentials (User ID & Password) in an encrypted format, which meets many organizations requirement for storing authentication information securely (i.e., non-plain text files like shell scripts or files protected only by Operating Systems permissions). Stash files replace the arsload.cfg configuration file used in versions of IBM Content Manager OnDemand prior to V9.0. | ||
arsstash can be used to store credentials for the [[arsload]] utility, OnDemand | arsstash can be used to store credentials for the [[arsload]] utility, OnDemand Distribution Facility, LDAP, or database passwords. This allows automated scripts (like scheduled jobs) to access Content Manager OnDemand without having to store passwords in clear-text inside shell scripts or files. | ||
== Related Articles == | == Related Articles == | ||
| Line 43: | Line 43: | ||
=== arsstash -a parameter === | === arsstash -a parameter === | ||
The -a parameter defines the action to be taken. | The -a parameter defines the action to be taken. | ||
; 1 | |||
: Stores an IBM CMOD User ID and password for usage with [[arsdoc]], [[arsadmin]], and other Content Manager OnDemand commands. | |||
; 2 | |||
: Deletes a previously stored User ID and password combination from the arsstash file. | |||
; 3 | |||
: Stores an IBM CMOD User ID and password pair for usage with the [[arsload]] command. | |||
: It is STRONGLY RECOMMENDED that you do not use the IBM CMOD Admin password with this option. Instead, create a new user, and assign it permission to add documents to specific Application Groups. | |||
; 4 | |||
: Stores a User ID & password for use with the IBM OnDemand Distribution Facility ("ODF"). | |||
; 5 | |||
: Stores a User ID & password for use with the IBM CMOD Report Distribution Facility. | |||
: The functionality of RDF has been integrated into ODF starting in Content Manager OnDemand v9.0. | |||
; 6 | |||
: Stores a User ID & password for use with PDD | |||
; 7 | |||
: Stores a User ID & password for use with Lightweight Directory Access Protocol | |||
: LDAP intergration with CMOD allows you to authenticate passwords from a central respository. | |||
; 8 | |||
: On systems with remote databases or forced password authentication, store the DB2 database User ID & password. | |||
: 9 | |||
: On systems with remote databases or forced password authentication, store the Oracle database User ID & password. | |||
If you don't specify the -u option with an action, OnDemand will display the currently assigned User ID stored in the stash file, and update the password. | |||
== Configuring ars.cfg for ars.stash == | |||
After the stash file is creates and contains the required credentials, you must configure IBM CMOD to use the stash file by modifying the ars.cfg configuration file to specify which stash file to use. | |||
== Using multiple stash files == | |||
== Assigning a stash file per-user == | |||
=== arsstash environment variables === | |||