Per user and global settings

The pdadmin policy commands can be set for a specific user (with the -user option) or globally (by not using the -user option). Any user-specific setting overrides a global setting for the policy.

We can also disable a policy (with the unset argument). With this setting, the policy contains no value.

Examples:

A global maximum concurrent web sessions policy of 1 session per user is created. As an exception to this policy, user brian is given a maximum concurrent web sessions policy of 4 sessions.

pdadmin> policy set max-concurrent-web-sessions 1
pdadmin> policy set max-concurrent-web-sessions 4 -user brian

pdadmin> policy get max-concurrent-web-sessions
Maximum concurrent web sessions: 1
pdadmin> policy get max-concurrent-web-sessions -user brian
Maximum concurrent web sessions: 4

***

The specific maximum concurrent web sessions policy for user brian is unset. User brian now has no maximum concurrent web sessions policy. However, user Brian is effectively governed by the current global maximum concurrent web sessions policy of 1 session.

pdadmin> policy set max-concurrent-web-sessions unset -user brian

pdadmin> policy get max-concurrent-web-sessions -user brian
Maximum concurrent web sessions: unset

***

The global maximum concurrent web sessions policy is unset. All users, including user brian, now have no maximum concurrent web sessions policy. However, the effective policy for all users is the same as the unlimited setting.

pdadmin> policy set max-concurrent-web-sessions unset

pdadmin> policy get max-concurrent-web-sessions
Maximum concurrent web sessions: unset

Parent topic: Set the maximum concurrent sessions policy