SAS 9.4 Management Console

Size: px
Start display at page:

Download "SAS 9.4 Management Console"

Transcription

1 SAS 9.4 Management Console Guide to Users and Permissions SAS Documentation

2 The correct bibliographic citation for this manual is as follows: SAS Institute Inc SAS 9.4 Management Console: Guide to Users and Permissions. Cary, NC: SAS Institute Inc. SAS 9.4 Management Console: Guide to Users and Permissions Copyright 2015, SAS Institute Inc., Cary, NC, USA All rights reserved. Produced in the United States of America. For a hardcopy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a web download or e-book:your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. U.S. Government License Rights; Restricted Rights: Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR , Commercial Computer Software-Restricted Rights (June 1987). SAS Institute Inc., SAS Campus Drive, Cary, North Carolina Electronic book 3, July 2015 SAS Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing web site at support.sas.com/publishing or call SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.

3 Contents Accessibility Features of SAS Management Console v Chapter 1 Concepts About This Document Introduction to User Administration Introduction to Access Management Chapter 2 User Administration Tasks Getting Information About a User Who Can Manage Users, Groups, and Roles? Add Users Add Administrators Manage Passwords Add Contact Information Create a Custom Group Create a Custom Role Change a Role's Capabilities Adjust Group or Role Membership Make a SAS Copy of DBMS Credentials Unlock an Internal Account Adjust Policies for an Internal Account Manage Authentication Domains Rename a User, Group, or Role Delete a User, Group, or Role Delegate Management of a Group or Role Include a User in Batch Synchronization Import or Export Users, Groups, and Roles Tips for Finding a User, Group, or Role Chapter 3 Exercises in User Administration Assign Capabilities to a Role Create and Use an Internal Account

4 iv Contents Chapter 4 Access Management Tasks Examining Permissions Who Can Set Permissions? Add an Explicit Grant or Denial Use an Access Control Template (ACT) Create a Custom ACT Update or Delete an ACT Set a Permission Condition (OLAP) Adjust the Repository-Level Settings Import or Export ACTs What Happens When I Select a Check Box? Tips for Efficiently Using Permissions Chapter 5 Exercises in Access Management Working with Explicit Controls Working with ACTs Working with Inherited Settings WriteMetadata and WriteMemberMetadata Glossary Index

5 v Accessibility Features of SAS Management Console Accessibility Overview For information about the accessibility of SAS Management Console, see the Help for that product. Documentation Format Please contact if you need this document in an alternative digital format.

6 vi Accessibility / Accessibility Features

7 1 1 Concepts About This Document Introduction to User Administration About User Administration About Users About Groups About Roles About Logins About Internal Accounts About Authentication Domains About Passwords About External Identities Uniqueness Requirements Introduction to Access Management About Access Management Granularity and Mechanics of Permissions Inheritance and Precedence of Permissions Use and Enforcement of Each Permission About This Document This document helps you administer users and permissions in SAS Management Console. It explains key concepts and provides step-by-step instructions for selected

8 2 Chapter 1 / Concepts tasks. For more information about security, see the SAS Intelligence Platform: Security Administration Guide. Introduction to User Administration About User Administration In order to make access distinctions and track user activity, security systems must know who is making each request. The primary purpose of user administration is to provide information that helps systems make this determination. The central piece of user information that the SAS environment requires is one external account ID for each user. The SAS environment uses its copy of these IDs to establish a unique SAS identity for each connecting user. All of a user's group memberships, role memberships, and permission assignments are ultimately tied to their SAS identity. Note: For identification purposes, only the account IDs are needed. SAS does not maintain copies of external passwords for identification purposes. To access user administration features in SAS Management Console, select the User Manager node on the Plug-ins tab. Your roles and permissions determine which user administration tasks you can perform. TIP As an alternative to interactively creating and maintaining identity information, you can write a program that performs these tasks as batch processes. See the user import macros documentation in the SAS Intelligence Platform: Security Administration Guide. About Users A user is an individual person or service identity. We recommend that you create an individual SAS identity for each person who uses the SAS environment. This enables you to make access distinctions in the metadata layer

9 and establishes a personal folder for each user. If generic access is sufficient for some of your users, those users can instead share the generic PUBLIC group identity. An individual SAS identity is established by coordination between two sets of identity information: in an external system, a user account in the metadata, a user definition that includes a copy of the external account ID To give someone an individual SAS identity, you create a metadata user definition that includes a copy of their external account ID. In the simplest configuration, each user needs an account that is known to the metadata server's host. If the metadata server is on Windows, users typically have Active Directory accounts. Introduction 3 If the metadata server is on UNIX, users might have UNIX accounts. Sometimes a UNIX host recognizes LDAP, Active Directory, or other types of accounts. Note: For information about alternate configurations (such as web authentication) and exceptions (such as SAS internal accounts), see SAS Intelligence Platform: Security Administration Guide. About Groups A group is a set of users. We recommend that you create groups to simplify security management as follows: It is more efficient to assign permissions to groups than to individual users. If you need to store passwords in the metadata, you can reduce the amount of required maintenance by using a group to make one shared account available to multiple users. It is sometimes more efficient to manage role membership by assigning groups to roles instead of assigning users directly to roles.

10 4 Chapter 1 / Concepts TIP A group's membership can include other groups as well as individual users. This enables you to create a nested group structure. This table introduces three predefined groups: Table 1.1 Group PUBLIC PUBLIC, SASUSERS, and SAS Administrators Description Implicitly includes everyone who can access the metadata server (directly or through a trust relationship). SASUSERS SAS Administrators Implicitly includes those members of the PUBLIC group who have a wellformed user definition. Should include only users who perform metadata administrative tasks. About Roles A role manages the availability of application features such as menu items. An application feature that is under role-based management is called a capability. Anyone who is a member of a role has all of that role's capabilities. This list highlights key points: Roles determine which user interface elements (such as menu items or plug-ins) you see when you use an application. Roles do not protect data or metadata (other than a few system items). Having a certain capability is not an alternative to meeting permission requirements. Permission requirements and capability requirements are cumulative. Roles and groups serve distinct purposes. You cannot assign permissions to a role or capabilities to a group. Capabilities are always additive. Assigning someone to a role never reduces what that person can do.

11 Introduction 5 Each application that supports roles provides one or more predefined roles. Each predefined role has a unique initial set of capabilities. The capabilities that a role provides should reflect the activities and responsibilities of that role's members. You can adjust the distribution of capabilities in these ways: Change role memberships. For example, to prevent regular users from seeing plugins in SAS Management Console, you might narrow the membership of the Management Console: Content Management role by making changes on that role's Members tab. Customize the initial roles-to-capabilities mapping by using any of these techniques: o o o Incrementally select or clear explicit capabilities for a role. You cannot deselect capabilities for the unrestricted role. Aggregate existing roles so that one or more roles contributes all of their capabilities to another role. Create new roles that provide unique combinations of capabilities. The following table introduces some of the predefined administrative roles: Table 1.2 Role Introduction to Selected Administrative Roles Capabilities Overview Metadata Server: Unrestricted Metadata Server: User Administration Management Console: Advanced Members have all capabilities and full access to metadata (but they cannot read other users passwords). Members can create and manage restricted users, groups, roles, internal accounts, logins, and authentication domains. Members can see all plug-ins in SAS Management Console. For details and exceptions, see the discussion of administrative roles in SAS Intelligence Platform: System Administration Guide.

12 6 Chapter 1 / Concepts About Logins What Is a Login? A login is a SAS copy of information about an external account. Every login must include a user ID. In a login for a Windows account, the ID must be qualified (for example, domain\user, or machine\user. TIP The requirement to provide a qualified ID for a Windows account applies to the SAS copy of the ID. It is usually not necessary to qualify the user ID that you provide when you launch a SAS application. Logins for Users Each user should have a login that establishes their SAS identity. It is not necessary to include a password in this login. For example, this is how Joe's login might look when a user administrator views Joe's Accounts tab: DefaultAuth WIN\Joe A user might have additional logins that provide access to other systems. For example, if Joe has his own Oracle account, he might have these two logins: DefaultAuth joe OracleAuth ORAjoe ******** Note: The Oracle login should include a copy of Joe's Oracle password. If a site uses web authentication, the requirements are different. For example, if Joe uses both web and desktop applications at such a site, Joe might have these three logins: DefaultAuth WIN\Joe OracleAuth ORAjoe ******** web WEBjoe Note: Like his DefaultAuth login, Joe's web login does not need to include a password.

13 Logins for Groups Groups do not have to have logins. The main reason to give a login to a group is to make a shared account available to multiple users. A group login contains a SAS copy of the user ID and password for a shared account. For example, to provide shared access to Oracle, a group might have a login that looks like this: OracleAuth sharedoraid ******** Introduction 7 All members of the group can see and use this login. Since this login is for a third-party database, a copy of the DBMS account password should be stored in this login. About Internal Accounts What Is an Internal Account? An internal account is a SAS account that the metadata server authenticates independently, without relying on an external authentication provider such as the operating system. Use internal accounts for only metadata administrators and certain service identities. Benefits of Internal Accounts Internal accounts have these advantages: Internal accounts provide an alternative to creating external accounts for SAS internal purposes such as inter-process communication. Internal accounts can be maintenance free. You do not have to synchronize internal accounts with some other user registry. Internal accounts do not have to conform to the security policies of the rest of your computing environment. For example, even if your host security policy forces password changes every 30 days, you can retain the initial policy for internal account passwords (which is that these passwords never expire). Internal accounts are usable only in the SAS realm, so they reduce exposure to the rest of your security environment.

14 8 Chapter 1 / Concepts Limitations of Internal Accounts Although the Create Internal Account button is available on all user definitions, internal accounts are not intended for regular users. Someone who has only an internal account cannot do these things: launch a standard workspace server without interactively providing some external credentials participate in Integrated Windows authentication or web authentication add, delete, initialize, or unregister a foundation repository Policies for Internal Accounts By initial policy, these server-level settings are in effect: Accounts do not expire and are not suspended due to inactivity. Passwords must be at least six characters, do not have to include mixed case or numbers, and do not expire. The five most recent passwords for an account cannot be reused for that account. There is no mandatory time delay between password changes. After three failed attempts to log on, an account is locked. If an account is locked because of logon failures, further log on attempts cannot be made for one hour. For an account that has a password expiration period, there is a forced password change on first use and after the password is reset by someone other than the account owner. By initial policy, passwords do not expire, so there are no forced password changes. Note: In User Manager, you can customize some of these settings on a per-account basis.

15 Introduction 9 About Authentication Domains What Is an Authentication Domain? An authentication domain is a name that facilitates the matching of logins with the servers for which they are valid. This matching is not important when you launch a client, but it is important when you access certain secondary servers such as a thirdparty DBMS or a standard workspace server. The second maintenance release of SAS 9.4 supports outbound and trusted authentication domains. A login in an outbound domain is used only to provide SAS applications with seamless access to external resources, such as a third-party vendor database. These logins are not part of the SAS identity phase that attempts to match the authenticated user ID to the current metadata user. Therefore, for outbound domain logins, the uniqueness requirements on the user ID are not enforced. A login in a trusted domain can be accessed only by a trusted user on behalf of the user. The identity to which the login is associated does not have direct access to the login (they will not see it listed on the Accounts tab in SAS Management Console). Instead, the login will be used on their behalf by a trusted user. A login in a trusted domain also requires the authentication domain to be an outbound domain. Administration of logins in outbound and trusted authentication domains can be performed only by unrestricted users and user administrators. For more information, see SAS Intelligence Platform: Security Administration Guide. When Do I Need to Add an Authentication Domain? In the simplest case, all logins and SAS servers are associated with one authentication domain (DefaultAuth). Here are some reasons for using more authentication domains: If you use web authentication, you might need a second authentication domain for the logins that contain web realm user IDs. If you want to provide seamless access to a third-party server (such as a DBMS server) that has its own user registry, you need a separate authentication domain for that server and its logins.

16 10 Chapter 1 / Concepts If both of the following criteria are met, you need a separate authentication domain for the standard workspace server and its logins: o o The standard workspace server does not share an authentication provider with the metadata server (and cannot be configured to do so). You want to provide seamless individualized access to the standard workspace server. About Passwords Passwords in Logins In general, it is not necessary to create a SAS copy of an external password. An exception is if you want to provide seamless access to a server that requires credentials that are different from the credentials that users initially submit. These are the most common examples: A third-party DBMS server might require a different set of credentials. In a multi-platform environment, the standard workspace server might require a different set of credentials. If credentials are not otherwise available, some applications prompt users for an appropriate user ID and password. Passwords in Internal Accounts Internal accounts exist only in the metadata. Each internal account includes a password. By initial policy, internal passwords do not expire. Passwords in Configuration Files Passwords for a few required accounts (such as the SAS Administrator and the SAS Trusted User) are included in configuration files. See the instructions for updating managed passwords in SAS Intelligence Platform: Security Administration Guide.

17 Introduction 11 About External Identities What Is an External Identity? An external identity is an optional synchronization key for a user, group, or role. If you use batch processes to coordinate SAS identity information with your primary user registry, you need external identities (such as employee IDs) to facilitate matching. This list explains the circumstances in which a user, group, or role needs an external identity: For a user, group, or role that you maintain interactively in SAS Management Console, no external identity is needed. For a user, group, or role that you maintain using batch processes, one external identity is needed. Where Do External Identities Come From? External identities can be added in these ways: For a user, group, or role that is created by an import process, an external identity is added as part of that process. For any user, group, or role, you can interactively add an external identity on the General tab of their definition. Uniqueness Requirements In metadata user administration, certain uniqueness requirements apply. For example, you cannot create a user definition that has the same name as an existing user definition and you cannot assign the same user ID to multiple users. For details, see SAS Intelligence Platform: Security Administration Guide.

18 12 Chapter 1 / Concepts Introduction to Access Management About Access Management Permissions that you set on an object s Authorization tab are part of a metadata-based access control system within the SAS Metadata Server. These permissions supplement protections in other layers, such as the operating system. Protections are cumulative across layers. You cannot perform a task unless you have sufficient access in all layers. CAUTION! Do not rely exclusively on metadata-layer permissions to protect data. Manage physical access in addition to metadata-layer access. See the discussion of access to SAS data in SAS Intelligence Platform: Security Administration Guide. Granularity and Mechanics of Permissions Repository-Level Controls Repository-level controls function as a gateway. Participating users should have the ReadMetadata and WriteMetadata permissions at the repository level. Repository-level controls also serve as a parent-of-last-resort, defining access to resources that do not have more specific settings. Repository-level controls are defined on the Permission Pattern tab of the repository ACT. In a standard configuration, the repository ACT is named Default ACT. Resource-Level Controls Resource-level controls manage access to a specific object such as a report, a stored process, a table, or a folder. You can define resource-level controls individually (as explicit settings) or in patterns (by using access control templates).

19 Fine-Grained Controls Fine-grained controls affect access to subsets of data within a resource. To establish fine-grained controls, you define permission conditions that filter data to constrain access. Feature-Level Controls Introduction 13 Some applications use roles to limit access to functionality. These applications check each user's roles in order to determine which menu items and features to display for that user. Roles are documented as part of user administration. Inheritance and Precedence of Permissions Two Relationship Networks Permission settings are conveyed across two distinct relationship networks, a resource network and an identity network. Permissions that are set directly on an object have priority over permissions that are set on the object s parent. For example, when access to a report is evaluated, a denial that is set on the report (and assigned to the PUBLIC group) overrides a grant that is set on the report's parent folder (even if the grant is assigned to you). The Resource Relationships Network Permissions that you set on one object can affect many other objects. For example, a report inherits permissions from the folder in which the report is located. The resource relationship network consists primarily of a folder tree. For details and exceptions, see the discussion of the metadata authorization model in SAS Intelligence Platform: Security Administration Guide. The Identity Relationships Network Permissions that you assign to one group can affect many other identities. For example, if you grant a group access to a table, that grant applies to all users who are members of the group. The identity relationship network is governed by a precedence order that starts with a primary identity, can incorporate multiple levels of nested group memberships, and ends with implicit memberships in SASUSERS and then PUBLIC.

20 14 Chapter 1 / Concepts If there is a tie in this network (for example, if you directly assign a user to two groups and give one group a grant and another group a denial), the outcome is a denial. Use and Enforcement of Each Permission General-Purpose Permissions The following table introduces the general-purpose permissions: Table 1.3 General-Purpose Permissions Permission (Abbreviation) ReadMetadata (RM) WriteMetadata (WM) WriteMemberMeta data (WMM) CheckInMetadata (CM) Actions Affected View an object. For example, to see a report, you need the ReadMetadata permission for that report. Edit, delete, or set permissions for an object. To delete an object, you also need the WriteMemberMetadata permission for the object s parent folder. Add an object to a folder or delete an object from a folder. To enable someone to interact with a folder's contents but with not the folder itself, grant WMM and deny WM. Check in and check out objects in a change-managed area. The CheckInMetadata permission is applicable only in SAS Data Integration Studio. Specialized Permissions The following table introduces some of the specialized permissions: Table 1.4 Specialized Permissions Permission (Abbreviation) Administer (A) Actions Affected Operate (monitor, stop, pause, resume, refresh, or quiesce) certain SAS servers and spawners.

21 Introduction 15 Permission (Abbreviation) Create (C) Read (R) Write (W) Delete (D) Actions Affected Add data through the metadata LIBNAME engine. Read data through certain objects (for example, cubes, information maps, and tables that are accessed through the metadata LIBNAME engine). Update data through certain objects (for example, data that is accessed through the metadata LIBNAME engine and publishing channels). Delete data through the metadata LIBNAME engine. Additional Information For more information, see the following documents: SAS Guide to Metadata-Bound Libraries (for information about the Insert, Update, Select, Create Table, Drop Table, and Alter Table permissions, and an additional use of the Delete permission) SAS Language Interfaces to Metadata (for information about the metadata LIBNAME engine) SAS Intelligence Platform: Security Administration Guide (for information about the metadata authorization layer)

22 16 Chapter 1 / Concepts

23 17 2 User Administration Tasks Getting Information About a User What Groups Is This User In? What Roles Is This User In? What Can This User Do? What Logins Are Available to This User? Does This User Have an External Identity? Does This User Have an Internal Account? Who Can Manage Users, Groups, and Roles? Add Users Add Administrators Manage Passwords Update the Password in a Login Reset an Internal Password Add Contact Information Create a Custom Group Why Create a Custom Group? How to Create a Custom Group Create a Custom Role Why Create a Custom Role? How to Create a Custom Role Change a Role's Capabilities

24 18 Chapter 2 / User Administration Tasks Adjust Group or Role Membership Make a SAS Copy of DBMS Credentials Store Shared Credentials for a DBMS Store Individual Credentials for a DBMS Unlock an Internal Account Adjust Policies for an Internal Account Manage Authentication Domains Add an Authentication Domain Rename an Authentication Domain Delete an Authentication Domain Rename a User, Group, or Role Delete a User, Group, or Role Delegate Management of a Group or Role Include a User in Batch Synchronization Import or Export Users, Groups, and Roles Tips for Finding a User, Group, or Role Getting Information About a User What Groups Is This User In? This list explains how group memberships are displayed for a user named Joe: direct groups If Joe is directly assigned to any groups, those assignments are displayed in the Member of list box on the Groups and Roles tab in Joe's Properties dialog box.

25 Getting Information About a User 19 indirect groups If Joe is a member of a group that is a member of another group, Joe is an indirect member of the second group. Because indirect membership is not displayed in Joe's Member of list box, you must check the properties of each group that Joe belongs to in order to determine whether that group is a member of another group. implicit groups If Joe has a well-formed user definition, he automatically belongs to both the PUBLIC and SASUSERS groups. These implicit memberships are not reflected in Joe's Member of list box. What Roles Is This User In? This list explains how role memberships are displayed for a user named Joe: direct roles If Joe is directly assigned to any roles, those assignments are displayed in the Member of list box on the Groups and Roles tab in Joe's Properties dialog box. indirect roles If Joe is a member of a group that is assigned to a role, Joe is an indirect member of that role. Because indirect membership is not displayed in Joe's Member of list box, you must check the properties of each group that Joe belongs to in order to determine whether that group is a member of any roles. Remember that Joe's Member of list box does not reflect his implicit membership in SASUSERS and PUBLIC. Users get most of their non-administrative capabilities through implicit membership in these groups. contributing roles If Joe is in a role that has contributing roles, Joe has the capabilities of the contributing roles. To determine whether a role has contributing roles, access the role's Properties dialog box and select the Contributing Roles tab.

26 20 Chapter 2 / User Administration Tasks What Can This User Do? Which Objects Can This User Access? Joe's access is not displayed as part of his user definition. Instead, Joe's permissions for a particular object are displayed on that object s Authorization tab. TIP SAS programmers can create reports that document access to resources. See the discussion of security report macros in the SAS Intelligence Platform: Security Administration Guide. Which Application Features Are Visible to This User? Joe has all of the capabilities that are provided by any of his roles. This list highlights key points about a role's Capabilities tab: Some roles provide implicit capabilities, which are not displayed. A capability that has a gray check box comes from a contributing role. These icons indicate the status of the items beneath a node in the tree: o A full tree icon indicates that all of the capabilities are assigned. o An empty tree icon indicates that none of the capabilities are assigned. o A partial tree icon indicates that some of the capabilities are assigned. What Logins Are Available to This User? This list explains how the logins that are available to a user named Joe are displayed: personal logins Joe's personal logins are displayed on the Accounts tab in his Properties dialog box. group logins A login that is assigned to a group can be used by any member of that group. Because Joe's group logins are not displayed on his Accounts tab, you must check

27 Who Can Manage Users, Groups, and Roles? 21 the properties of each group that Joe belongs to in order to determine whether any of those groups have logins. Note: Logins are visible only if you have user administration capabilities, you are looking at your own user definition, or you are looking at a group that you belong to. Does This User Have an External Identity? To determine whether a user has an external identity, click the External Identities button on the user's General tab. Does This User Have an Internal Account? To determine whether a user has an internal account, examine the bottom of the user's Accounts tab. If a user has an internal account, their internal ID is listed in that location. Regular users usually do not have internal accounts. Note: Internal accounts are visible only if you have user administration capabilities or you are looking at your own user definition. Who Can Manage Users, Groups, and Roles? The following table summarizes the permissions and capabilities that are required for selected user administration tasks in SAS Management Console. Table 2.1 Minimum Requirements by Task Task Set Create, update, or delete your own logins. Requirements The User Manager capability.

28 22 Chapter 2 / User Administration Tasks Task Set Create, update, or delete restricted identities. Create or delete an unrestricted user. Change memberships of an unrestricted user. Make changes to the Metadata Server: Unrestricted role. Requirements The User Manager capability. User administration capabilities (provided implicitly by the Metadata Server: User Administration role). The WriteMetadata permission (for existing identities, software component objects that provide role capabilities, and the repository). Unrestricted status (provided implicitly by the Metadata Server: Unrestricted role). Here are some additional details: In the initial configuration, user administration privileges are distributed as follows: o o o All registered users can update their own logins. Members of the SAS Administrators group can add and manage restricted identities. Only one user, the SAS Administrator, can add and manage unrestricted identities. As an alternative to using SAS Management Console to update your logins, you can use SAS Personal Login Manager (a stand-alone desktop utility). You can delegate management of an existing group or role to someone who does not have user administration capabilities. See Delegate Management of a Group or Role on page 36. Add Users To create an individual SAS identity:

29 Add Administrators 23 1 On the Plug-ins tab, select User Manager. 2 For each user: a b Right-click and select New User. On the General tab, enter a name. TIP We recommend that you avoid using spaces or special characters in the name of a user, group, or role that you create. Not all components support spaces and special characters in identity names. c On the Accounts tab, click New. In the New Login dialog box, select the appropriate authentication domain (for example, DefaultAuth ) and enter the user's external account ID. It is not necessary to include a password in this login. Note: If the user ID is for a Windows account, you must qualify the ID (for example, WIN\user or d Click OK to save the new login. Click OK again to save the new user. 3 (Optional) Use the Groups and Roles tab to make a user a direct member of another group or a role. Note: The user automatically belongs to PUBLIC (everyone who can access the environment) and SASUSERS (those members of PUBLIC who have a well-formed user definition). Note: You do not have to make changes on the user's Authorization tab. This tab has no effect on what the user can do. Add Administrators To create an individual SAS identity that is based on an internal account:

30 24 Chapter 2 / User Administration Tasks 1 On the Plug-ins tab, select User Manager. Make sure that you are in the foundation repository. 2 For each administrator: a b Right-click and select New User. On the General tab, enter a name. Note: The administrator's internal user ID is based on this name, so it is a good idea to use a short identifier. TIP You cannot change the name of an identity after it is saved. You can instead add or change the display name of an identity. c On the Accounts tab, click Create Internal Account. In the New Internal Account dialog box, enter and confirm an initial password. Note: By initial policy, internal passwords must be at least six characters, do not have to include mixed case or numbers, and do not expire. TIP If you want to force a password change on first use, set a password expiration period. d e On the Groups and Roles tab, move the SAS Administrators group to the Member of list box. This makes the new user a member of SAS Administrators. Click OK to save the new administrator. 3 (Optional) To verify your work, examine the SAS Administrators group: a b In the main display, select the SAS Administrators group, right-click, and select Properties. On the Members tab, verify that the new administrators are in the Current Members list box.

31 Manage Passwords 25 c On the Groups and Roles tab, verify that the Member of list box includes the expected administrative role memberships. In a standard configuration, members of the SAS Administrators group are able to perform almost all administrative tasks. For details, see SAS Intelligence Platform: System Administration Guide. This list highlights key points: You do not have to use internal accounts for your administrators. You can choose to give an administrator an external account and a corresponding login as you would for a regular user. When you log on with an internal account, remember to include suffix (for example, A few administrative tasks (such as importing and exporting physical content) use a standard workspace server. Someone who has only an internal account cannot perform such tasks without interactively providing external credentials. Manage Passwords Passwords for a few required accounts (such as the SAS Administrator and the SAS Trusted User) are included in configuration files. If these passwords change, you must also update the configuration. See the SAS Intelligence Platform: Security Administration Guide. Update the Password in a Login Password management for logins is driven by changes that occur in other systems. For example, if you have a personal login for a third-party DBMS, and you change your DBMS password, you must also update the SAS copy of that password. Note: Most logins do not include passwords, so this is not an extremely common task. Note: Each user can update their own logins as necessary in SAS Personal Login Manager. 1 Select the user (or group) whose external password has changed.

32 26 Chapter 2 / User Administration Tasks 2 Right-click and select Properties. 3 On the Accounts tab, select the login that you need to update and click Edit. Note: Only someone who has user administration capabilities can see logins that do not belong to them. 4 In the Login Properties dialog box, enter and confirm the new password. Reset an Internal Password Note: Typically, each administrator updates their own internal password as necessary (in SAS Management Console or SAS Personal Login Manager). 1 Select the user whose internal password you want to reset. 2 Right-click and select Properties. 3 At the bottom of the user's Accounts tab, click Update. Note: If this button is not present, the user does not have an internal account. Internal accounts are intended for only metadata administrators and certain service identities. 4 In the user's Internal Account Properties dialog box, enter and confirm a new password. Note: By initial policy, internal passwords must be at least six characters, do not have to include mixed case or numbers, and do not expire. 5 If you are resetting someone else's password, inform the owner of the account that their password has been reset and tell them what the new password is.

33 Create a Custom Group 27 Add Contact Information Some application features can use contact information that is stored in user definitions. 1 Select the user whose phone number, address, or location you want to store. Note: You cannot store contact information for groups or roles. 2 Right-click and select Properties. 3 On the General tab, select the , Phone, or Address tab and then click New. 4 In the Properties dialog box, enter contact information. TIP If you batch synchronize users and want to preserve contact information that you enter interactively, use a consistent value in the Type field. In your synchronization code, you can use this value to define exceptions that exclude this data from the batch update. TIP If you want a user to receive SMS text message notifications from the alert system, you must add SMS as an entry for their phone number. You can add SMS in the Type field on the Phone Properties window in SAS Management Console. Create a Custom Group Why Create a Custom Group? Most predefined groups are either very broad (PUBLIC, SASUSERS) or very narrow and highly privileged (SAS Administrators). Create more groups for these reasons:

34 28 Chapter 2 / User Administration Tasks To manage permissions for distinct classes of access. For example, you might create a group for each business unit or functional area of responsibility. To make a shared credential available to multiple users. See Store Shared Credentials for a DBMS on page 33. How to Create a Custom Group 1 On the Plug-ins tab, select User Manager and make sure you are in the correct repository. 2 Right-click and select New Group. 3 In the Properties dialog box: a On the General tab, enter a name. TIP We recommend that you avoid using spaces or special characters in the name of a user, group, or role that you create. Not all components support spaces and special characters in identity names. b c d On the Members tab, assign user or groups to the new group. If you want to make this group a member of other groups or roles, use the Groups and Roles tab. If you are using this group to make a shared account available, add a shared login on the Accounts tab. Note: You do not have to make changes on the group's Authorization tab. This tab has no effect on what the group can do.

35 Create a Custom Role 29 Create a Custom Role Why Create a Custom Role? In many cases, the predefined roles are sufficient. You might choose to create additional roles for these reasons: To decrease the level of granularity by creating an umbrella role that aggregates two or more existing roles. For example, you might create a role that includes all capabilities other than those of the most privileged roles. To increase the level of granularity by creating a mini-role that provides only a subset of the capabilities of a predefined role. For example, you might create a custom role called Report Distribution that provides only the report scheduling and distribution capabilities for SAS Web Report Studio. To create a cross-application role for a particular type of functionality. For example, you might create an OLAP role that includes the OLAP capabilities from SAS Enterprise Guide and the SAS Add-In for Microsoft Office. How to Create a Custom Role 1 On the Plug-ins tab, select User Manager. 2 Right-click and select New Role. 3 In the Properties dialog box: a On the General tab, enter a name. TIP We recommend that you avoid using spaces or special characters in the name of a user, group, or role that you create. Not all components support spaces and special characters in identity names.

36 30 Chapter 2 / User Administration Tasks b c On the Members tab, assign users and groups to the role. Define the role's capabilities using either or both of these techniques: Assign capabilities to the role by selecting check boxes on the Capabilities tab. Clicking a tree icon changes the status of the selections beneath that icon's node. Give this role all of the capabilities of one or more other roles by using the Contributing Roles tab. For example, to create a role that includes all capabilities other than those of the most privileged roles, select the Contributing Roles tab, move all roles over and then move the metadata server roles back. Note: Changes that you make to a role's capabilities affect any roles to which that role contributes its capabilities. Note: You cannot selectively assign or incrementally remove a contributed capability. Note: You do not have to make changes on the role's Authorization tab. This tab has no effect on what the role can do. Change a Role's Capabilities CAUTION! There is no automated method for reverting a role back to its original set of capabilities. The initial capabilities-to-roles mapping is appropriate in many cases. Instead of adjusting the capabilities of a predefined role, consider creating a new role. To change the set of capabilities that a role provides: 1 Make sure you have a current backup. 2 In User Manager, select the role. 3 Right-click and select Properties.

37 Change a Role's Capabilities 31 4 Use either or both of these techniques: Incrementally add or remove capabilities from the role by selecting or clearing check boxes on the Capabilities tab. Note: A capability that has gray shading behind its check box contributing role and cannot be removed individually. comes from a Note: If you click a selected white check box (because you want to clear that check box) and you then see a selected gray check box, your removal of the explicit assignment has revealed an underlying contributed capability. Note: You cannot deselect capabilities for the unrestricted role. Give the role the capabilities of one or more other roles by using the Contributing Roles tab. Note: These relationships are dynamic; changes that you make to a role's capabilities affect any roles to which that role contributes its capabilities. Note: You cannot selectively assign or incrementally remove a contributed capability. This list provides details about the Capabilities tab: The metadata server administrative roles include implicit capabilities, which are not displayed on this tab. The tree icons indicate the status of the items beneath a node in the tree. Clicking a tree icon changes the status of the selections beneath that icon's node. The status cycles between full, empty, and partial states, with these exceptions: o The empty state does not occur if there are contributed capabilities. o The partial state occurs only if the original settings were mixed (some capabilities selected, some capabilities not selected). Note: The original settings are a cache of the selections that were in place at the time that you first click a particular tree icon. Any intervening action (such as clicking a check box or clicking the tree icon for a different node) causes

38 32 Chapter 2 / User Administration Tasks an update to the original settings cache. There is no cache of earlier states. If you want to undo all of your changes, click Cancel. 5 (Optional) On the General tab, update the role's description to reflect its revised capabilities. 6 Click OK to save the changes to the role. Adjust Group or Role Membership 1 In User Manager, select the group or role whose membership you want to change. 2 Right-click and select Properties. 3 On the Members tab, add or remove identities from the group or role. Note: The Current Members list box displays only direct members. Note: You cannot make a role a member of a group or of another role. You can instead make one role contribute all of its capabilities to another role. Note: On a group definition, do not confuse the Members tab with the Groups and Roles tab. Use a group's Groups and Roles tab only if you want to make that group a member of other groups or roles. TIP You can filter the contents of the Available Members list box by using the Search radio button. Make a SAS Copy of DBMS Credentials To provide seamless access to a third-party DBMS, add a login that contains the user ID and password for a DBMS account. These instructions are also appropriate for

39 Make a SAS Copy of DBMS Credentials 33 providing seamless access to other servers that require credentials that are different from the credentials with which a user initially logs on. Store Shared Credentials for a DBMS 1 Verify the authentication domain for the DBMS: a b On the Plug-ins tab, expand the Server Manager node and select the DBMS server. In the display area, right-click the server's connection object, select Properties, and access the Options tab. Note which authentication domain is specified. 2 In User Manager, identify or create the group that you will use to manage the shared DBMS account that you want to share. For example, if you want all users to share the account, use the PUBLIC group. 3 On the group's Accounts tab, click New. 4 In the New Login Properties dialog box: a Enter the user ID and password for the DBMS account. b Select the authentication domain that you saw in step 1b. c Click OK to save the login. 5 On the group's Members tab, make sure that everyone who needs to use the shared account is a member. Remember that only direct memberships are displayed, but indirect or implicit membership is also sufficient for making the credentials available. Store Individual Credentials for a DBMS Follow the instructions in the preceding topic but add the login to a user's Accounts tab instead of a group's Accounts tab.

40 34 Chapter 2 / User Administration Tasks Note: If a user has more than one available login in a particular authentication domain, the login that is closest to the user is used. If there is a tie (for example, if a user is a direct member of two groups and both groups have logins in the same authentication domain), then the same login is used consistently, but you cannot control which of the two logins is used. Unlock an Internal Account By initial policy, three consecutive failed attempts to log on with an internal account locks that account for one hour. To immediately unlock a locked internal account: 1 In User Manager, select the user whose internal account is locked. Right-click and select Properties. 2 Select the Accounts tab. In the confirmation message box, click Yes. Adjust Policies for an Internal Account You can use per-account settings to selectively override some of the server-level policies for internal accounts. 1 On the user's Accounts tab, click Update to open the Internal Account Properties dialog box. 2 Make changes in the Custom Settings group box. Note: There are two distinct expiration settings. Do not confuse the account expiration date with the password expiration period. TIP A few required accounts (such as the SAS Administrator and the SAS Trusted User) are included in configuration files. To minimize administrative effort,

41 Manage Authentication Domains 35 do not add expiration dates to these accounts or expiration periods to these passwords. Manage Authentication Domains Add an Authentication Domain 1 On the Plug-ins tab, select User Manager (or Server Manager). 2 Right-click and select Authentication Domains. Note: This menu item is available only if you have user administration capabilities. 3 In the Authentication Domains Management dialog box, click New. 4 In the New Authentication Domain dialog box, enter a name. Rename an Authentication Domain CAUTION! Changing the name of an authentication domain can interfere with single sign-on. Do not rename an authentication domain unless you need to make a correction. To change the name of an authentication domain, select a row in the Authentication Domains Management dialog box and click Edit. Delete an Authentication Domain CAUTION! When you delete an authentication domain, all of the logins in that authentication domain are deleted. Before you delete an authentication domain, make sure you have a current backup. To delete an authentication domain, select a row in the Authentication Domains Management dialog box and click Delete.

42 36 Chapter 2 / User Administration Tasks Rename a User, Group, or Role You can add or change the display name of an identity. 1 In User Manager, select the user, group, or role that you want to rename. 2 Right-click and select Properties. 3 On the General tab, add or edit text in the Display Name field. For an identity that does not have a display name, the name serves as the display name. Delete a User, Group, or Role CAUTION! When you delete a user, group, or role, you lose all of that identity's metadata associations. Creating a new identity with the same name does not restore those associations. 1 Select the user, group, or role that you want to delete. 2 Right-click and select Delete. In the confirmation message box, click Yes. Delegate Management of a Group or Role To delegate management to someone who does not have user administration capabilities, use direct grants of the WriteMetadata permission. For example, to delegate management of a group named ETL Developers to a user named Tara, you would access the Authorization tab for the ETL Developers group, add Tara, and explicitly grant the WriteMetadata permission to her.

43 Import or Export Users, Groups, and Roles 37 Note: Do not assume that someone who has only indirect settings on someone else's Authorization tab has not been delegated management. The best way to check for delegation of an identity is to check each entry in the Users and Groups list box on that identity's Authorization tab to see whether there are any explicit or ACT grants of the WriteMetadata permission. Include a User in Batch Synchronization Note: Only users, groups, and roles that have an external identity can participate in batch synchronization. The external identity serves as a synchronization key. 1 Select the user, right-click, and select Properties. 2 On the user's General tab, click External Identities. 3 Click New. In the Identifier field, enter a value that identifies the user in your external source. CAUTION! An inaccurate external identity value can cause inadvertent deletion of an identity during the synchronization process. Make sure that any external identity value that you add corresponds to a key ID value in the tables that you extract from your primary user registry. Note: SAS does not enforce uniqueness when you store external identity values. Note: The synchronization process uses only the first external identity in each list. Import or Export Users, Groups, and Roles You can use the standard metadata import and export framework to copy identities.

44 38 Chapter 2 / User Administration Tasks You initiate these actions on the Folders tab under SAS Folders System Security. For detailed instructions, see SAS Intelligence Platform: System Administration Guide. TIP Do not confuse these promotion tools with the user import macros that help you create and synchronize metadata identities from an external provider, such as Active Directory. The user import macros are documented in SAS Intelligence Platform: Security Administration Guide. Tips for Finding a User, Group, or Role This list explains how you can modify the User Manager display of users, groups, and roles: To sort the list of identities in ascending or descending order, click a column heading. To revert to the order in which identities were added to the repository, right-click a column heading and select Sort Original. To hide a column, right-click the column heading and select Hide Column. To show a hidden column, right-click any column heading and select Show the column name. To change the width of a column, click and drag the edge of the column heading. To move a column, click and drag the column heading. To set a different default view, select the User Manager node on the Plug-ins tab, right-click, and select Options. To limit the type of identities displayed, clear the Show Users, Show Groups, or Show Roles check boxes. To filter the list of identities displayed, select the Search radio button.

45 Note: The User, Group, or Role column lists display names. For an identity that does not have a display name, the name is listed instead. To find an identity in the User Manager display: 1 Make sure the correct repository is selected at the top of the Plug-ins tab. 2 Ensure that the appropriate Show check box is selected. Tips for Finding a User, Group, or Role 39 3 If you cannot easily locate the identity, select the Search radio button, specify criteria, and click Search Now. The generated list includes all identities that meet all of the specified criteria. To specify additional criteria, click Advanced. When advanced search criteria are applied, a yellow symbol appears on the Advanced button.

46 40 Chapter 2 / User Administration Tasks

47 41 3 Exercises in User Administration Assign Capabilities to a Role Create and Use an Internal Account Assign Capabilities to a Role To practice customizing the distribution of capabilities across roles, complete this exercise in SAS Management Console: 1 Log on as someone who has user administration capabilities and is a member of the SAS Administrators group (for example, 2 On the Plug-ins tab, select User Manager (make sure you are in the foundation repository). In the display area, clear the Show Users and Show Groups check boxes. The roles that exist in your deployment are displayed. 3 Right-click User Manager and select New Role. On the General tab, enter Test Role in the Name field. Note: Creating a new role isolates this exercise from the rest of your deployment, ensuring that your current configuration is preserved. 4 To learn how to directly assign capabilities, select the Capabilities tab:

48 42 Chapter 3 / Exercises in User Administration a Notice that a message at the top of the tab reminds you that a few capabilities (for example, those of the metadata server's roles) are not listed on this tab (because those capabilities are implicit). b Notice that the first node (Applications) has an empty branch icon. This indicates that no explicit capabilities are assigned to this role. c d Notice that there is a second-level node for each component that provides explicit capabilities. A role can provide capabilities from multiple applications. Click + to expand the Management Console node. Click + to expand the Plugins node. Select the Authorization Manager check box. Notice that the branch icons are now partial. This indicates that some of the capabilities are selected. Note: To see a description of any capability, click that capability's text and look at the Description field at the bottom of the tab. e Click the partial icon for the Plug-ins folder. This action causes all of the capabilities beneath that node to be explicitly selected. Click again to cycle back to the empty branch icon (no capabilities assigned). Click a third time to revert to the immediately preceding state (only the Authorization Manager check box selected). f Click the Authorization Manager check box to clear it. 5 To learn how to indirectly assign capabilities, select the Contributing Roles tab: a b In the Available Roles list, select Management Console: Content Management. Before you make this a contributing role, verify its capabilities. Move the Management Console: Content Management role to the Current Roles list. This role now contributes all of its capabilities to your new role. If capabilities of this contributing role change, the capabilities of your test role change also. It is necessary to use contributing roles in these circumstances:

49 Create and Use an Internal Account 43 You want to extend implicit capabilities (like the capabilities of the metadata server roles) to other roles. You want to provide dynamic aggregation of roles so that changes to one role propagate to other roles that have the first role as a contributing role. 6 To learn about interactions between contributed and directly assigned capabilities, select your test role's Capabilities tab again. a b c d Under Management Console Plug-ins, notice that capabilities from the Management Console: Content Management role are now selected. A gray circle icon identifies these as contributed capabilities. Select the already-selected Authorization Manager check box. This adds a direct assignment on top of the contributed assignment, making the assignment independent from the underlying contributing role. Click the tree icon for the Plug-ins folder three times (stop when only the Authorization Manager check box is explicitly selected). Select the Authorization Manager check box again. It reverts back to the contributed state. You cannot incrementally remove a contributed capability. 7 To close the dialog box (and not save the test role), click Cancel. Create and Use an Internal Account To practice creating and using an internal account, complete this exercise in SAS Management Console: 1 Log on as someone who has user administration capabilities (for example, 2 On the Plug-ins tab, select User Manager.

50 44 Chapter 3 / Exercises in User Administration 3 Right-click User Manager and select New User. On the General tab, enter a short word such as test in the Name field. 4 On the Accounts tab, click Create Internal Account. In the New Internal Account dialog box: a Notice that the user ID is constructed from the name that you entered on the General tab and suffix. b Enter and confirm a simple initial password such as Note: These instructions assume that the default server-level policies for internal accounts are in place. c d Select the Set a custom password expiration period check box and the never expires radio button. Click OK to save the new internal account. 5 Notice that the new account appears at the bottom of the Accounts tab. Click OK to save the new user. 6 Log on to SAS Management Console as the new internal user: a b c d From the main menu, select File Connection Profile. In the informational message box, click Yes. In the Connection Profile dialog box, select Create a new connection profile and click OK. In the Connection Profile wizard, name the profile internal, provide the machine name and port of the metadata server, and enter the internal credentials (for example, and ). Select the Save user ID and password in this profile check box. Click Finish. In the Connection Profile dialog box, click OK.

51 Create and Use an Internal Account 45 7 Notice that you have the permissions and capabilities of the SASUSERS and PUBLIC groups (because you did not make any additional group or role assignments for the test user). Note: To clean up, log back on as someone who has user administration capabilities. In User Manager, delete the user that you created for this exercise. To delete the test user's home directory and MyFolder, select the Folders tab, navigate to SAS Folders Users, right-click the test folder, and select Delete. Note: There are no server configuration activities for SAS internal authentication. The metadata server always accepts valid internal account credentials. However, internal accounts are intended for only metadata administrators and certain service accounts. Internal accounts are not intended for regular users.

52 46 Chapter 3 / Exercises in User Administration

53 47 4 Access Management Tasks Examining Permissions How to Interpret the Authorization Tab How to Check the Permissions of an Unlisted User Which Items are Parents to This Object? Who Can Set Permissions? Add an Explicit Grant or Denial Use an Access Control Template (ACT) Why Use ACTs? How to Use an ACT Create a Custom ACT Why Create Custom ACTs? How to Create a Custom ACT Update or Delete an ACT Set a Permission Condition (OLAP) Adjust the Repository-Level Settings Why Adjust the Repository-Level Settings? Make Changes to the Repository ACT Designate a Different ACT to Serve as the Repository ACT Import or Export ACTs What Happens When I Select a Check Box?

54 48 Chapter 4 / Access Management Tasks Tips for Efficiently Using Permissions Assign Permissions to Groups Use Folders to Organize Content Centralize Permissions with ACTs Deny Broadly, Grant Selectively (To the Extent Possible) Examining Permissions You cannot view someone's permissions by looking at their user definition. To view someone s permissions, navigate instead to an object or container that you are interested in, open the Properties dialog box, and select the Authorization tab. How to Interpret the Authorization Tab The List of Names The Users and Groups list box includes only those users and groups who participate in the current object's settings. An identity participates if they are included in any of these places: the repository ACT's Permission Pattern tab a setting that this object inherits from a parent object an applied ACT's Permission Pattern tab an explicit setting on the object Note: You cannot remove identities that participate through the repository ACT, an applied ACT, or an inherited setting. Any restricted user who is not listed has the access of their closest listed group. For each unlisted user, group memberships and identity precedence determine which listed group is closest. For example, the closest listed group for an administrator might be SAS Administrators, and the closest listed group for a regular user might be SASUSERS. For a full discussion of identity precedence, see SAS Intelligence Platform: Security Administration Guide.

55 Examining Permissions 49 The List of Permissions The Effective Permissions list box displays the metadata layer access that the selected user or group has to the current object. Effective permissions are a calculation of the net effect of all applicable permission settings. Effective permissions do not reflect role-based constraints or access controlled in other layers such as the operating system. This table explains the significance of the check box colors: Table 4.1 Significance of Color in the Permissions List Color Term Significance (clear) Explicit The permission is set on the current object and assigned to the selected identity. (green) ACT The permission comes from an applied ACT whose pattern explicitly assigns the grant or denial to the selected identity. (gray) Indirect The permission comes from someone else (the unrestricted role or a group that has an explicit or ACT setting) or somewhere else (a parent object or the repository ACT).* * For the WriteMemberMetadata permission, gray means that the setting either mirrors the setting for the WriteMetadata permission or is derived from group settings.

SAS 9.3 Management Console

SAS 9.3 Management Console SAS 9.3 Management Console Guide to Users and Permissions SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc 2011. SAS 9.3 Management Console: Guide to

More information

SAS 9.2 Management Console. Guide to Users and Permissions

SAS 9.2 Management Console. Guide to Users and Permissions SAS 9.2 Management Console Guide to Users and Permissions The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2009. SAS ) 9.2 Management Console: Guide to Users and Permissions.

More information

SAS 9.3 Intelligence Platform

SAS 9.3 Intelligence Platform SAS 9.3 Intelligence Platform Security Administration Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2011. SAS 9.3 Intelligence Platform: Security

More information

SAS 9.4 Intelligence Platform

SAS 9.4 Intelligence Platform SAS 9.4 Intelligence Platform Security Administration Guide Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2013. SAS 9.4 Intelligence

More information

SAS Business Data Network 3.1

SAS Business Data Network 3.1 SAS Business Data Network 3.1 User s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. SAS Business Data Network 3.1: User's Guide. Cary,

More information

SAS Marketing Automation 5.1. User s Guide

SAS Marketing Automation 5.1. User s Guide SAS Marketing Automation 5.1 User s Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2007. SAS Marketing Automation 5.1: User s Guide. Cary, NC: SAS Institute

More information

Scheduling in SAS 9.3

Scheduling in SAS 9.3 Scheduling in SAS 9.3 SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc 2011. Scheduling in SAS 9.3. Cary, NC: SAS Institute Inc. Scheduling in SAS 9.3

More information

SAS IT Resource Management 3.2

SAS IT Resource Management 3.2 SAS IT Resource Management 3.2 Reporting Guide Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc 2011. SAS IT Resource Management 3.2:

More information

SAS 9.3 Intelligence Platform

SAS 9.3 Intelligence Platform SAS 9.3 Intelligence Platform System Administration Guide Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2012. SAS 9.3 Intelligence

More information

Guide to Operating SAS IT Resource Management 3.5 without a Middle Tier

Guide to Operating SAS IT Resource Management 3.5 without a Middle Tier Guide to Operating SAS IT Resource Management 3.5 without a Middle Tier SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. Guide to Operating SAS

More information

SAS. Cloud. Account Administrator s Guide. SAS Documentation

SAS. Cloud. Account Administrator s Guide. SAS Documentation SAS Cloud Account Administrator s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. SAS Cloud: Account Administrator's Guide. Cary, NC:

More information

SAS Task Manager 2.2. User s Guide. SAS Documentation

SAS Task Manager 2.2. User s Guide. SAS Documentation SAS Task Manager 2.2 User s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS Task Manager 2.2: User's Guide. Cary, NC: SAS Institute

More information

Scheduling in SAS 9.4 Second Edition

Scheduling in SAS 9.4 Second Edition Scheduling in SAS 9.4 Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. Scheduling in SAS 9.4, Second Edition. Cary, NC: SAS Institute

More information

9.1 SAS/ACCESS. Interface to SAP BW. User s Guide

9.1 SAS/ACCESS. Interface to SAP BW. User s Guide SAS/ACCESS 9.1 Interface to SAP BW User s Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2004. SAS/ACCESS 9.1 Interface to SAP BW: User s Guide. Cary, NC: SAS

More information

SAS BI Dashboard 4.3. User's Guide. SAS Documentation

SAS BI Dashboard 4.3. User's Guide. SAS Documentation SAS BI Dashboard 4.3 User's Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2010. SAS BI Dashboard 4.3: User s Guide. Cary, NC: SAS Institute

More information

SAS Add-In 2.1 for Microsoft Office: Getting Started with Data Analysis

SAS Add-In 2.1 for Microsoft Office: Getting Started with Data Analysis SAS Add-In 2.1 for Microsoft Office: Getting Started with Data Analysis The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2007. SAS Add-In 2.1 for Microsoft Office: Getting

More information

SAS 9.3 Intelligence Platform

SAS 9.3 Intelligence Platform SAS 9.3 Intelligence Platform Application Server Administration Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc 2011. SAS SAS 9.3 Intelligence

More information

SAS. 9.1.3 Intelligence Platform. System Administration Guide

SAS. 9.1.3 Intelligence Platform. System Administration Guide SAS 9.1.3 Intelligence Platform System Administration Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2006. SAS 9.1.3 Intelligence Platform: System Administration

More information

Technical Paper. Defining an ODBC Library in SAS 9.2 Management Console Using Microsoft Windows NT Authentication

Technical Paper. Defining an ODBC Library in SAS 9.2 Management Console Using Microsoft Windows NT Authentication Technical Paper Defining an ODBC Library in SAS 9.2 Management Console Using Microsoft Windows NT Authentication Release Information Content Version: 1.0 October 2015. Trademarks and Patents SAS Institute

More information

SAS 9.4 Intelligence Platform

SAS 9.4 Intelligence Platform SAS 9.4 Intelligence Platform Application Server Administration Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2013. SAS 9.4 Intelligence Platform:

More information

OnDemand for Academics

OnDemand for Academics SAS OnDemand for Academics User s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS OnDemand for Academics: User's Guide. Cary, NC:

More information

Implementing a SAS Metadata Server Configuration for Use with SAS Enterprise Guide

Implementing a SAS Metadata Server Configuration for Use with SAS Enterprise Guide Implementing a SAS Metadata Server Configuration for Use with SAS Enterprise Guide Step 1: Setting Up Required Users and Groups o Windows Operating Systems Only Step 2: Installing Software Using the SAS

More information

Implementing a SAS 9.3 Enterprise BI Server Deployment TS-811. in Microsoft Windows Operating Environments

Implementing a SAS 9.3 Enterprise BI Server Deployment TS-811. in Microsoft Windows Operating Environments Implementing a SAS 9.3 Enterprise BI Server Deployment TS-811 in Microsoft Windows Operating Environments Table of Contents Introduction... 1 Step 1: Create a SAS Software Depot..... 1 Step 2: Prepare

More information

SAS Visual Analytics 7.1 for SAS Cloud. Quick-Start Guide

SAS Visual Analytics 7.1 for SAS Cloud. Quick-Start Guide SAS Visual Analytics 7.1 for SAS Cloud Quick-Start Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. SAS Visual Analytics 7.1 for SAS Cloud: Quick-Start Guide.

More information

WatchDox Administrator's Guide. Application Version 3.7.5

WatchDox Administrator's Guide. Application Version 3.7.5 Application Version 3.7.5 Confidentiality This document contains confidential material that is proprietary WatchDox. The information and ideas herein may not be disclosed to any unauthorized individuals

More information

SAS 9.4 Intelligence Platform

SAS 9.4 Intelligence Platform SAS 9.4 Intelligence Platform Installation and Configuration Guide Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS 9.4 Intelligence

More information

P R O V I S I O N I N G O R A C L E H Y P E R I O N F I N A N C I A L M A N A G E M E N T

P R O V I S I O N I N G O R A C L E H Y P E R I O N F I N A N C I A L M A N A G E M E N T O R A C L E H Y P E R I O N F I N A N C I A L M A N A G E M E N T, F U S I O N E D I T I O N R E L E A S E 1 1. 1. 1.x P R O V I S I O N I N G O R A C L E H Y P E R I O N F I N A N C I A L M A N A G E

More information

SAS BI Dashboard 3.1. User s Guide

SAS BI Dashboard 3.1. User s Guide SAS BI Dashboard 3.1 User s Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2007. SAS BI Dashboard 3.1: User s Guide. Cary, NC: SAS Institute Inc. SAS BI Dashboard

More information

Communications Access Methods for SAS/CONNECT 9.3 and SAS/SHARE 9.3 Second Edition

Communications Access Methods for SAS/CONNECT 9.3 and SAS/SHARE 9.3 Second Edition Communications Access Methods for SAS/CONNECT 9.3 and SAS/SHARE 9.3 Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2012. Communications

More information

SAS 9.3 Open Metadata Interface: Reference and Usage

SAS 9.3 Open Metadata Interface: Reference and Usage SAS 9.3 Open Metadata Interface: Reference and Usage SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2011. SAS 9.3 Open Metadata Interface: Reference

More information

SAS BI Dashboard 4.4. User's Guide Second Edition. SAS Documentation

SAS BI Dashboard 4.4. User's Guide Second Edition. SAS Documentation SAS BI Dashboard 4.4 User's Guide Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2013. SAS BI Dashboard 4.4: User's Guide, Second

More information

SAS 9.4 PC Files Server

SAS 9.4 PC Files Server SAS 9.4 PC Files Server Installation and Configuration Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. SAS 9.4 PC Files Server: Installation

More information

Oracle Enterprise Single Sign-on Provisioning Gateway. Administrator Guide Release 10.1.4.1.0 E12613-01

Oracle Enterprise Single Sign-on Provisioning Gateway. Administrator Guide Release 10.1.4.1.0 E12613-01 Oracle Enterprise Single Sign-on Provisioning Gateway Administrator Guide Release 10.1.4.1.0 E12613-01 March 2009 Oracle Enterprise Single Sign-on Provisioning Gateway, Administrator Guide, Release 10.1.4.1.0

More information

Microsoft Project Server 2010 Administrator's Guide

Microsoft Project Server 2010 Administrator's Guide Microsoft Project Server 2010 Administrator's Guide 1 Copyright This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references,

More information

SAS 9.3 Logging: Configuration and Programming Reference

SAS 9.3 Logging: Configuration and Programming Reference SAS 9.3 Logging: Configuration and Programming Reference SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2011. SAS 9.3 Logging: Configuration and

More information

Oracle Human Capital Management Cloud Securing Oracle HCM Cloud. Release 10

Oracle Human Capital Management Cloud Securing Oracle HCM Cloud. Release 10 Oracle Human Capital Management Cloud Release 10 Oracle Human Capital Management Cloud Part Number E61339-03 Copyright 2011-2015, Oracle and/or its affiliates. All rights reserved. Authors: Suzanne Kinkead,

More information

User Installation Guide for SAS 9.1 Foundation for 64-bit Microsoft Windows

User Installation Guide for SAS 9.1 Foundation for 64-bit Microsoft Windows User Installation Guide for SAS 9.1 Foundation for 64-bit Microsoft Windows Installation Instructions Where to Begin SAS Setup Wizard Repair or Remove SAS Software Glossary Where to Begin Most people who

More information

Sage Intelligence Financial Reporting for Sage ERP X3 Version 6.5 Installation Guide

Sage Intelligence Financial Reporting for Sage ERP X3 Version 6.5 Installation Guide Sage Intelligence Financial Reporting for Sage ERP X3 Version 6.5 Installation Guide Table of Contents TABLE OF CONTENTS... 3 1.0 INTRODUCTION... 1 1.1 HOW TO USE THIS GUIDE... 1 1.2 TOPIC SUMMARY...

More information

www.novell.com/documentation Administration Guide Novell Filr 1.0.1 May 2014

www.novell.com/documentation Administration Guide Novell Filr 1.0.1 May 2014 www.novell.com/documentation Administration Guide Novell Filr 1.0.1 May 2014 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation,

More information

Connect for Dragon Medical 360 Network Edition. Administrator Guide

Connect for Dragon Medical 360 Network Edition. Administrator Guide Connect for Dragon Medical 360 Network Edition Administrator Guide Copyright 2013. Connect for Dragon Medical 360 Network Edition. Nuance Communications, Inc. has patents or pending patent applications

More information

EPM Performance Suite Profitability Administration & Security Guide

EPM Performance Suite Profitability Administration & Security Guide BusinessObjects XI R2 11.20 EPM Performance Suite Profitability Administration & Security Guide BusinessObjects XI R2 11.20 Windows Patents Trademarks Copyright Third-party Contributors Business Objects

More information

IT Service Level Management 2.1 User s Guide SAS

IT Service Level Management 2.1 User s Guide SAS IT Service Level Management 2.1 User s Guide SAS The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2006. SAS IT Service Level Management 2.1: User s Guide. Cary, NC:

More information

User Management Guide

User Management Guide AlienVault Unified Security Management (USM) 4.x-5.x User Management Guide USM v4.x-5.x User Management Guide, rev 1 Copyright 2015 AlienVault, Inc. All rights reserved. The AlienVault Logo, AlienVault,

More information

Managing users. Account sources. Chapter 1

Managing users. Account sources. Chapter 1 Chapter 1 Managing users The Users page in Cloud Manager lists all of the user accounts in the Centrify identity platform. This includes all of the users you create in the Centrify for Mobile user service

More information

Citrix Systems, Inc.

Citrix Systems, Inc. Citrix Password Manager Quick Deployment Guide Install and Use Password Manager on Presentation Server in Under Two Hours Citrix Systems, Inc. Notice The information in this publication is subject to change

More information

Novell ZENworks 10 Configuration Management SP3

Novell ZENworks 10 Configuration Management SP3 AUTHORIZED DOCUMENTATION Software Distribution Reference Novell ZENworks 10 Configuration Management SP3 10.3 November 17, 2011 www.novell.com Legal Notices Novell, Inc., makes no representations or warranties

More information

TREENO ELECTRONIC DOCUMENT MANAGEMENT. Administration Guide

TREENO ELECTRONIC DOCUMENT MANAGEMENT. Administration Guide TREENO ELECTRONIC DOCUMENT MANAGEMENT Administration Guide October 2012 Contents Introduction... 8 About This Guide... 9 About Treeno... 9 Managing Security... 10 Treeno Security Overview... 10 Administrator

More information

SAS 9.3 Foundation for Microsoft Windows

SAS 9.3 Foundation for Microsoft Windows Software License Renewal Instructions SAS 9.3 Foundation for Microsoft Windows Note: In this document, references to Microsoft Windows or Windows include Microsoft Windows for x64. SAS software is licensed

More information

Delegated Administration Quick Start

Delegated Administration Quick Start Delegated Administration Quick Start Topic 50200 Delegated Administration Quick Start Updated 22-Oct-2013 Applies to: Web Filter, Web Security, Web Security Gateway, and Web Security Gateway Anywhere,

More information

Permissions Management for Site Admins

Permissions Management for Site Admins ControlPoint Publication Date: April 29, 2015 All Rights Reserved. This software is protected by copyright law and international treaties. Unauthorized reproduction or distribution of this software, or

More information

Security Explorer 9.5. User Guide

Security Explorer 9.5. User Guide 2014 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement.

More information

Oracle Enterprise Manager. Description. Versions Supported

Oracle Enterprise Manager. Description. Versions Supported Oracle Enterprise Manager System Monitoring Plug-in Installation Guide for Microsoft Active Directory 10g Release 2 (10.2.0.2) B28044-02 June 2006 This document provides a brief description about the Oracle

More information

SAS 9.4 Logging. Configuration and Programming Reference Second Edition. SAS Documentation

SAS 9.4 Logging. Configuration and Programming Reference Second Edition. SAS Documentation SAS 9.4 Logging Configuration and Programming Reference Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. SAS 9.4 Logging: Configuration

More information

Administering Group Policy with Group Policy Management Console

Administering Group Policy with Group Policy Management Console Administering Group Policy with Group Policy Management Console By Jim Lundy Microsoft Corporation Published: April 2003 Abstract In conjunction with Windows Server 2003, Microsoft has released a new Group

More information

WhatsUp Gold v16.2 Installation and Configuration Guide

WhatsUp Gold v16.2 Installation and Configuration Guide WhatsUp Gold v16.2 Installation and Configuration Guide Contents Installing and Configuring Ipswitch WhatsUp Gold v16.2 using WhatsUp Setup Installing WhatsUp Gold using WhatsUp Setup... 1 Security guidelines

More information

Grid Computing in SAS 9.4 Third Edition

Grid Computing in SAS 9.4 Third Edition Grid Computing in SAS 9.4 Third Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. Grid Computing in SAS 9.4, Third Edition. Cary, NC:

More information

EMC Documentum Webtop

EMC Documentum Webtop EMC Documentum Webtop Version 6.5 User Guide P/N 300 007 239 A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748 9103 1 508 435 1000 www.emc.com Copyright 1994 2008 EMC Corporation. All rights

More information

User Guide. IntraLinks Courier Plug-in for Microsoft Outlook

User Guide. IntraLinks Courier Plug-in for Microsoft Outlook IntraLinks Courier Plug-in for Microsoft Outlook User Guide Copyright 2012 IntraLinks, Inc. Version 3.2 September 2012 IntraLinks 24/7/365 support US: 212 543 7800 UK: +44 (0) 20 7623 8500 See IntraLinks

More information

GP REPORTS VIEWER USER GUIDE

GP REPORTS VIEWER USER GUIDE GP Reports Viewer Dynamics GP Reporting Made Easy GP REPORTS VIEWER USER GUIDE For Dynamics GP Version 2015 (Build 5) Dynamics GP Version 2013 (Build 14) Dynamics GP Version 2010 (Build 65) Last updated

More information

Master Data Services. SQL Server 2012 Books Online

Master Data Services. SQL Server 2012 Books Online Master Data Services SQL Server 2012 Books Online Summary: Master Data Services (MDS) is the SQL Server solution for master data management. Master data management (MDM) describes the efforts made by an

More information

ProSystem fx Engagement

ProSystem fx Engagement ProSystem fx Engagement Admin Guide October 2009 Copyright 2009 CCH INCORPORATED. A Wolters Kluwer business. All Rights Reserved. Material in this publication may not be reproduced or transmitted, in any

More information

StarTeam/CaliberRM LDAP QuickStart Manager 2009. Administration Guide

StarTeam/CaliberRM LDAP QuickStart Manager 2009. Administration Guide StarTeam/CaliberRM LDAP QuickStart Manager 2009 Administration Guide Borland Software Corporation 8310 N Capital of Texas Bldg 2, Ste 100 Austin, TX 78731 USA http://www.borland.com Borland Software Corporation

More information

Configuring BEA WebLogic Server for Web Authentication with SAS 9.2 Web Applications

Configuring BEA WebLogic Server for Web Authentication with SAS 9.2 Web Applications Configuration Guide Configuring BEA WebLogic Server for Web Authentication with SAS 9.2 Web Applications This document describes how to configure Web authentication with BEA WebLogic for the SAS Web applications.

More information

DIGIPASS Authentication for Citrix Access Gateway VPN Connections

DIGIPASS Authentication for Citrix Access Gateway VPN Connections DIGIPASS Authentication for Citrix Access Gateway VPN Connections With VASCO Digipass Pack for Citrix 2006 VASCO Data Security. All rights reserved. Page 1 of 31 Integration Guideline Disclaimer Disclaimer

More information

NovaBACKUP. Storage Server. NovaStor / May 2011

NovaBACKUP. Storage Server. NovaStor / May 2011 NovaBACKUP Storage Server NovaStor / May 2011 2011 NovaStor, all rights reserved. All trademarks are the property of their respective owners. Features and specifications are subject to change without notice.

More information

ecopy Connector for EMC Documentum

ecopy Connector for EMC Documentum ecopy Connector for EMC Documentum Version 4.0 for ecopy ShareScan OP Administrator s Guide Part Number: 73-00218 (4/2007) Licensing, Copyright, and Trademark Information The information in this document

More information

Virtual Data Centre. User Guide

Virtual Data Centre. User Guide Virtual Data Centre User Guide 2 P age Table of Contents Getting Started with vcloud Director... 8 1. Understanding vcloud Director... 8 2. Log In to the Web Console... 9 3. Using vcloud Director... 10

More information

ADP Workforce Now Security Guide. Version 2.0-1

ADP Workforce Now Security Guide. Version 2.0-1 ADP Workforce Now Security Guide Version 2.0-1 ADP Trademarks The ADP logo, ADP, and ADP Workforce Now are registered trademarks of ADP, Inc. Third-Party Trademarks Microsoft, Windows, and Windows NT are

More information

Xcalibur. Foundation. Administrator Guide. Software Version 3.0

Xcalibur. Foundation. Administrator Guide. Software Version 3.0 Xcalibur Foundation Administrator Guide Software Version 3.0 XCALI-97520 Revision A May 2013 2013 Thermo Fisher Scientific Inc. All rights reserved. LCquan, Watson LIMS, and Web Access are trademarks,

More information

QUANTIFY INSTALLATION GUIDE

QUANTIFY INSTALLATION GUIDE QUANTIFY INSTALLATION GUIDE Thank you for putting your trust in Avontus! This guide reviews the process of installing Quantify software. For Quantify system requirement information, please refer to the

More information

eopf Release E Administrator Training Manual

eopf Release E Administrator Training Manual eopf Release E Administrator Training Manual i The United States Office Of Personnel Management eopf Administrator Training Manual for eopf v5 eopf Version 4.1, July 2007, March 2008, March 2009; eopf

More information

PRODUCT WHITE PAPER LABEL ARCHIVE. Adding and Configuring Active Directory Users in LABEL ARCHIVE

PRODUCT WHITE PAPER LABEL ARCHIVE. Adding and Configuring Active Directory Users in LABEL ARCHIVE PRODUCT WHITE PAPER LABEL ARCHIVE Adding and Configuring Active Directory Users in LABEL ARCHIVE TEKLYNX International March 19, 2010 Introduction Now more than ever, businesses large and small alike are

More information

Shavlik Patch for Microsoft System Center

Shavlik Patch for Microsoft System Center Shavlik Patch for Microsoft System Center User s Guide For use with Microsoft System Center Configuration Manager 2012 Copyright and Trademarks Copyright Copyright 2014 Shavlik. All rights reserved. This

More information

vcloud Director User's Guide

vcloud Director User's Guide vcloud Director 5.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of

More information

Oracle Enterprise Manager. Description. Versions Supported

Oracle Enterprise Manager. Description. Versions Supported Oracle Enterprise Manager System Monitoring Plug-in Installation Guide for Microsoft SQL Server Release 10 (4.0.3.1.0) E14811-03 June 2009 This document provides a brief description about the Oracle System

More information

Extending the Metadata Security Audit Reporting Capabilities of the Audit and Performance Measurement Package October 2010

Extending the Metadata Security Audit Reporting Capabilities of the Audit and Performance Measurement Package October 2010 Extending the Metadata Security Audit Reporting Capabilities of the Audit and Performance Measurement Package October 2010 ENTERPRISE EXCELLENCE CENTER Table of Contents 1 Introduction... 1 2 Metadata

More information

Instructions for Configuring a SAS Metadata Server for Use with JMP Clinical

Instructions for Configuring a SAS Metadata Server for Use with JMP Clinical Instructions for Configuring a SAS Metadata Server for Use with JMP Clinical These instructions describe the process for configuring a SAS Metadata server to work with JMP Clinical. Before You Configure

More information

SourceForge Enterprise Edition 4.4 SP1 User Guide

SourceForge Enterprise Edition 4.4 SP1 User Guide SourceForge Enterprise Edition 4.4 SP1 User Guide SourceForge Enterprise Edition 4.4, Service Pack 1 Part Number: 98-0063 Last Revision: January 2008 Copyright 2008 CollabNet, Inc. All rights reserved.

More information

End User Configuration

End User Configuration CHAPTER114 The window in Cisco Unified Communications Manager Administration allows the administrator to add, search, display, and maintain information about Cisco Unified Communications Manager end users.

More information

Chapter 15: Forms. User Guide. 1 P a g e

Chapter 15: Forms. User Guide. 1 P a g e User Guide Chapter 15 Forms Engine 1 P a g e Table of Contents Introduction... 3 Form Building Basics... 4 1) About Form Templates... 4 2) About Form Instances... 4 Key Information... 4 Accessing the Form

More information

Configuration Guide. SafeNet Authentication Service. SAS Agent for Microsoft Internet Information Services (IIS)

Configuration Guide. SafeNet Authentication Service. SAS Agent for Microsoft Internet Information Services (IIS) SafeNet Authentication Service Configuration Guide Technical Manual Template Release 1.0, PN: 000-000000-000, Rev. A, March 2013, Copyright 2013 SafeNet, Inc. All rights reserved. 1 Document Information

More information

1. PROJECT MANAGEMENT INTRO

1. PROJECT MANAGEMENT INTRO Table of Contents Project Management Intro................................... 3 Project Set Up & Maintenance............................... 4 User Accounts............................................ 19

More information

The United States Office Of Personnel Management eopf System Administrator Training Manual for eopf Version 4.0.

The United States Office Of Personnel Management eopf System Administrator Training Manual for eopf Version 4.0. The United States Office Of Personnel Management eopf System Administrator Training Manual for eopf Version 4.0. Copyright 1994-2007 by Northrop Grumman. All rights reserved. Northrop Grumman, the Northrop

More information

CA ARCserve Backup for Windows

CA ARCserve Backup for Windows CA ARCserve Backup for Windows Agent for Microsoft SharePoint Server Guide r15 This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for

More information

TU04. Best practices for implementing a BI strategy with SAS Mike Vanderlinden, COMSYS IT Partners, Portage, MI

TU04. Best practices for implementing a BI strategy with SAS Mike Vanderlinden, COMSYS IT Partners, Portage, MI TU04 Best practices for implementing a BI strategy with SAS Mike Vanderlinden, COMSYS IT Partners, Portage, MI ABSTRACT Implementing a Business Intelligence strategy can be a daunting and challenging task.

More information

Document Management Getting Started Guide

Document Management Getting Started Guide Document Management Getting Started Guide Version: 6.6.x Written by: Product Documentation, R&D Date: February 2011 ImageNow and CaptureNow are registered trademarks of Perceptive Software, Inc. All other

More information

GoldKey Software. User s Manual. Revision 7.12. WideBand Corporation www.goldkey.com. Copyright 2007-2014 WideBand Corporation. All Rights Reserved.

GoldKey Software. User s Manual. Revision 7.12. WideBand Corporation www.goldkey.com. Copyright 2007-2014 WideBand Corporation. All Rights Reserved. GoldKey Software User s Manual Revision 7.12 WideBand Corporation www.goldkey.com 1 Table of Contents GoldKey Installation and Quick Start... 5 Initial Personalization... 5 Creating a Primary Secure Drive...

More information

Microsoft Dynamics CRM Adapter for Microsoft Dynamics GP

Microsoft Dynamics CRM Adapter for Microsoft Dynamics GP Microsoft Dynamics Microsoft Dynamics CRM Adapter for Microsoft Dynamics GP May 2010 Find updates to this documentation at the following location. http://go.microsoft.com/fwlink/?linkid=162558&clcid=0x409

More information

Using LDAP Authentication in a PowerCenter Domain

Using LDAP Authentication in a PowerCenter Domain Using LDAP Authentication in a PowerCenter Domain 2008 Informatica Corporation Overview LDAP user accounts can access PowerCenter applications. To provide LDAP user accounts access to the PowerCenter applications,

More information

Citrix EdgeSight for Load Testing User s Guide. Citrix EdgeSight for Load Testing 3.8

Citrix EdgeSight for Load Testing User s Guide. Citrix EdgeSight for Load Testing 3.8 Citrix EdgeSight for Load Testing User s Guide Citrix EdgeSight for Load Testing 3.8 Copyright Use of the product documented in this guide is subject to your prior acceptance of the End User License Agreement.

More information

ORACLE USER PRODUCTIVITY KIT USAGE TRACKING ADMINISTRATION & REPORTING RELEASE 3.6 PART NO. E17087-01

ORACLE USER PRODUCTIVITY KIT USAGE TRACKING ADMINISTRATION & REPORTING RELEASE 3.6 PART NO. E17087-01 ORACLE USER PRODUCTIVITY KIT USAGE TRACKING ADMINISTRATION & REPORTING RELEASE 3.6 PART NO. E17087-01 FEBRUARY 2010 COPYRIGHT Copyright 1998, 2009, Oracle and/or its affiliates. All rights reserved. Part

More information

Training Module 1: Administration (logical) (for Privia version 5.9)

Training Module 1: Administration (logical) (for Privia version 5.9) Training Module : Administration (logical) (for Privia version.9) Copyright 0 by Privia LLC. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval

More information

Oracle Enterprise Single Sign-on Logon Manager How-To: Configuring ESSO-LM Event Logging with Microsoft SQL Server 2005 Release 11.1.1.2.

Oracle Enterprise Single Sign-on Logon Manager How-To: Configuring ESSO-LM Event Logging with Microsoft SQL Server 2005 Release 11.1.1.2. Oracle Enterprise Single Sign-on Logon Manager How-To: Configuring ESSO-LM Event Logging with Microsoft SQL Server 2005 Release 11.1.1.2.0 20413-01 December 2010 8B Oracle Enterprise Single Sign-on Logon

More information

Synchronization Agent Configuration Guide

Synchronization Agent Configuration Guide SafeNet Authentication Service Synchronization Agent Configuration Guide 1 Document Information Document Part Number 007-012476-001, Revision A Release Date July 2014 Trademarks All intellectual property

More information

Getting Started. Getting Started with Time Warner Cable Business Class. Voice Manager. A Guide for Administrators and Users

Getting Started. Getting Started with Time Warner Cable Business Class. Voice Manager. A Guide for Administrators and Users Getting Started Getting Started with Time Warner Cable Business Class Voice Manager A Guide for Administrators and Users Table of Contents Table of Contents... 2 How to Use This Guide... 3 Administrators...

More information

User s Guide For Department of Facility Services

User s Guide For Department of Facility Services Doc s File Server User s Guide For Department of Facility Services For Ver : 7.2.88.1020 Rev : 1_05-27-2011 Created by : Elliott Jeyaseelan 2 Table of Contents SERVER LOGIN & AUTHENTICATION REQUIREMENTS

More information

Universal Management Service 2015

Universal Management Service 2015 Universal Management Service 2015 UMS 2015 Help All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording,

More information

USERS MANUAL FOR OWL A DOCUMENT REPOSITORY SYSTEM

USERS MANUAL FOR OWL A DOCUMENT REPOSITORY SYSTEM USERS MANUAL FOR OWL A DOCUMENT REPOSITORY SYSTEM User Manual Table of Contents Introducing OWL...3 Starting to use Owl...4 The Logging in page...4 Using the browser...6 Folder structure...6 Title Bar...6

More information

WhatsUp Gold v16.1 Installation and Configuration Guide

WhatsUp Gold v16.1 Installation and Configuration Guide WhatsUp Gold v16.1 Installation and Configuration Guide Contents Installing and Configuring Ipswitch WhatsUp Gold v16.1 using WhatsUp Setup Installing WhatsUp Gold using WhatsUp Setup... 1 Security guidelines

More information

CA Performance Center

CA Performance Center CA Performance Center Single Sign-On User Guide 2.4 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is

More information