Welcome, if you are looking for support on One Identity products, please visit One Identity Portal.

Authentication Services 4.1 - Quest Single Sign-on for SAP Integration Guide

One Identity Privileged Access Suite for Unix

One Identity Privileged Access Suite for Unix
Unix Security Simplified

Privileged Access Suite for Unix solves the inherent security and administration issues of Unix-based systems (including Linux® and Mac OS X®) while making satisfying compliance requirements a breeze. It unifies and consolidates identities, assigns individual accountability and enables centralized reporting for user and administrator access to Unix. The Privileged Access Suite for Unix is a one-stop shop for Unix security that combines an Active Directory bridge and root delegation solutions under a unified console that grants organizations centralized visibility and streamlined administration of identities and access rights across their entire Unix environment.

Active Directory Bridge

Achieve unified access control, authentication, authorization and identity administration for Unix, Linux®, and Mac OS X® systems by extending them into Active Directory (AD) and taking advantage of AD’s inherent benefits. Patented technology allows non-Windows® resources to become part of the AD trusted realm, and extends AD’s security, compliance and Kerberos-based authentication capabilities to Unix, Linux®, and Mac OS X®. (See https://www.quest.com/products/authentication-services/ for more information about the Active Directory Bridge product.)

Root Delegation

The Privileged Access Suite for Unix offers two different approaches to delegating the Unix root account. The suite either enhances or replaces sudo, depending on your needs.

  • By choosing to enhance sudo, you will keep everything you know and love about sudo while enhancing it with features like a central sudo policy server, centralized keystroke logs, a sudo event log, and compliance reports for who can do what with Sudo.

    (See https://www.quest.com/products/privilege-manager-for-sudo/ for more information about enhancing sudo.)

  • By choosing to replace sudo, you will still be able to delegate the Unix root privilege based on centralized policy reporting on access rights, but with a more granular permission and the ability to log keystrokes on all activities from the time a user logs in, not just the commands that are prefixed with "sudo". In addition, this option implements several additional security features like restricted shells, remote host command execution, and hardened binaries that remove the ability to escape out of commands and gain undetected elevated access.

    (See https://www.quest.com/products/privilege-manager-for-unix/ for more information about replacing sudo.)

Privileged Access Suite for Unix

Privileged Access Suite for Unix offers two editions - Standard edition and Advanced edition. Both editions include: Management Console for Unix®, a common mangement console that provides a consolidated view and centralized point of management for local Unix users and groups; and, Authentication Services, patented technology that enables organizations to extend the security and compliance of Active Directory to Unix, Linux®, and Mac OS X® platforms and enterprise applications. In addition

  • The Standard edition licenses you for Privilege Manager for Sudo.
  • The Advanced edition licenses you for Privilege Manager for Unix®.

Quest recommends that you follow these steps:

  1. Install Authentication Services on one machine, so you can set up your Active Directory Forest.
  2. Install Management Console for Unix®, so you can perform all the other installation steps from the mangement console.
  3. Add and profile host(s) using the mangement console.
  4. Configure the console to use Active Directory.
  5. Deploy client software to remote hosts.

    Depending on which Privileged Access Suite for Unix edition you have purchased, deploy either:

    • Privilege Manager for Unix® software (that is, Privilege Manager Agent packages)

      -OR-

    • Privilege Manager for Sudo software (that is, Sudo Plugin packages)

Was this topic helpful?

[Select Rating]



About This Guide

The Single Sign-on for SAP Integration Guide is intended for system administrators, network administrators, consultants, analysts, and any other IT professionals who will be using Single Sign-on for SAP to provide seamless authentication to SAP® using the Active Directory credentials of the logged-on user. This guide walks you through the installation and configuration process.

Note: The term "Unix" is used informally throughout the Authentication Services documentation to denote any operating system that closely resembles the trademarked system, UNIX®.


Was this topic helpful?

[Select Rating]



Introducing Single Sign-on for SAP

Introducing Single Sign-on for SAP

SAP® systems host critical enterprise applications. In today's regulatory environment, the ability to secure access to these applications, and to secure the transmission of their data, is an increasingly important compliance and security requirement.

The Authentication Services Single Sign-on for SAP solution integrates SAP® solutions with Active Directory. Using the identity and security infrastructure available with Active Directory, organizations can implement tight identity integration between SAP® and Active Directory user accounts allowing users to securely authenticate with SAP® applications using their desktop login credentials. This eliminates the need to re-enter (or remember) a separate SAP® username and password.

You can use these same credentials to implement secure data transmission among SAP® modules and the SAP® GUI client. Sensitive enterprise information that is exchanged between the user's desktop and the remote SAP® Application Server is automatically encrypted, securing it from any network eavesdropping.

Authentication Services provides a solution that complies with the functional requirements of the SAP® SNC interface. The ability of Authentication Services to directly join Unix systems with the Active Directory domain is what makes the tight integration and single sign-on experience possible.

SAP® SNC makes use of the GSS-API provided by Authentication Services on the SAP® Application Server side. The SAP® GUI client on the Windows® desktop also uses GSS-API through the Single Sign-on for SAP extensions.


Was this topic helpful?

[Select Rating]



SAP Secure Network Communications (SNC)

Introducing Single Sign-on for SAP > SAP Secure Network Communications (SNC)

Secure Network Communications (SNC) is designed to allow external security mechanisms (such as Authentication Services) to integrate with the SAP® environment to provide additional security features. By integrating the SAP® system through standard protocols such as GSS-API, SNC allows you to isolate SAP® applications from the specifics of the authentication and security implementation. SNC provides three aspects of security: authentication; data integrity; and data security.

The authentication feature provides for secure authentication using an external security token such as a Kerberos ticket which allows single sign-on.

With the data integrity feature enabled, the system detects any changes or manipulation of the data which may have occurred between the two end points of a communication.

The data security or privacy protection feature encrypts message transmission making them resistant to network eavesdropping. This feature also includes data integrity support.

The level of security to be applied to the environment is determined by the SNC configuration as described in the SAP® document, Secure Network Communications: SNC User's Guide.


Was this topic helpful?

[Select Rating]



Self Service Tools
Knowledge Base
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
Related Documents