21.4 Identity Managers

The Moab identity manager interface can be used to coordinate global and local information regarding users, groups, accounts, and classes associated with compute resources. The identity manager interface may also be used to allow Moab to automatically and dynamically create and modify user accounts and credential attributes according to current workload needs.

21.4.1 Identity Manager Overview

Moab allows sites extensive flexibility when it comes to defining credential access, attributes, and relationships. In most cases, use of the USERCFG, GROUPCFG, ACCOUNTCFG, CLASSCFG, and QOSCFG parameters is adequate to specify the needed configuration. However, in certain cases such as the following, this approach may not be ideal or even adequate:

Moab addresses these and similar issues through the use of an identity manager. An identity manager is configured with the IDCFG parameter and allows Moab to exchange information with an external identity management service. As with Moab resource manager interfaces, this service can be a full commercial package designed for this purpose, or something far simpler such as a web service, text file, or database.

21.4.2 Basic Configuration

Configuring an identity manager in basic read-only mode can be accomplished by simply setting the SERVER attribute. If Moab is to interact with the identity manager in read/write mode, some additional configuration may be required.

One or more comma-delimited object types from the following list: acct, group, or user
If specified, Moab will block all jobs associated with credentials not explicitly reported in the most recent identity manager update. If the credential appears on subsequent updates, resource access will be immediately restored.
NoteJobs will only be blocked if fairshare is enabled. This can be accomplished by setting the FSPOLICY parameter to any value such as in the following example:
IDCFG[test01] BLOCKCREDLIST acct,user
Moab will block any jobs associated with accounts or users not in the most recent identity manager update.
minute, hour, day, or infinity (default is infinity)
If specified, Moab refreshes identity manager information once every specified iteration. If infinity is specifed, the information is updated only at Moab start up.
Moab queries the identity manager every hour.
One or more comma-delimited object types from the following list: acct, group, or user
If specified, Moab will reset the account access list and fairshare cap and target for all credentials of the specified type(s) regardless of whether they are included in the current info manager report. Moab will then load information for the specified credentials.
Moab will reset the account access list and fairshare target for all groups.
Specifies the protocol/interface to use to contact the identity manager.
IDCFG[test01] SERVER=exec://$HOME/example.pl
Moab will use example.pl to communicate with the identity manager.
<BOOLEAN> (default is FALSE)
When an IDCFG script fails, it retries almost immediately and continuously until it succeeds. When UPDATEREFRESHONFAILURE is set to TRUE, a failed script does not attempt to rerun immediately, but instead follows the specified REFRESHPERIOD schedule. When set to TRUE, UPDATEREFRESHONFAILURE updates the script execution timestamp, even if the script does not end successfully.
IDCFG[info] SERVER=exec:///home/tshaw/test/1447/bad_script.pl REFRESHPERIOD=hour UPDATEREFRESHONFAILURE=TRUE

21.4.3 Importing Credential Fairness Policies

One common use for an identity manager is to import fairness data from a global external information service. As an example, assume a site needed to coordinate Moab group level fairshare targets with an allocation database that constrains total allocations available to any given group. To enable this, a configuration like the following might be used:

IDCFG[alloc] SERVER=exec://$TOOLSDIR/idquery.pl

The tools/idquery.pl script could be set up to query a local database and report its results to Moab. Each iteration, Moab will then import this information, adjust its internal configuration, and immediately respect the new fairness policies.

21.4.4 Identity Manager Data Format

When an identity manager outputs credential information either through an exec or file based interface, the data should be organized in the following format:



Note To clear a comment, set its value to ""; for example: comment="".


The following output may be generated by an exec based identity manager:

group:financial fstarget=16.3 alist=project2
group:marketing fstarget=2.5
group:engineering fstarget=36.7
group:dm fstarget=42.5
user:jason adminlevel=3
account:sales maxnode=128 maxjob=8,16

The following example limits user bob to 8 matlab generic resources.

user:bob MAXGRES[matlab]=8
Note To specify unlimited use of generic resources, set the value to -1.

21.4.5 Identity Manager Conflicts

When local credential configuration (as specified via moab.cfg) conflicts with identity manager configuration, the identity manager value takes precedence and the local values are overwritten.

21.4.6 Refreshing Identity Manager Data

By default, Moab only loads identity manager information once when it is first started up. If the identity manager data is dynamic, then you may want Moab to periodically update its information. To do this, set the REFRESHPERIOD attribute of the IDCFG parameter. Legal values are documented in the following table:

Value Description
update identity information once per minute
update identity information once per hour
update identity information once per day
update identity information only at start-up (default)


IDCFG[hq] SERVER=exec://$TOOLSDIR/updatepolicy.sh REFRESHPERIOD=hour
Note Job credential feasibility is evaluated at job submission and start time.

See Also

Copyright © 2012 Adaptive Computing Enterprises, Inc.®