Skip to main contentSkip to search
Powered by Zoomin Software. For more details please contactZoomin
Progress DocumentationProgress Documentation
Progress Documentation
  • Home
  • Home
  • EnglishČeštinaDeutsch (Germany)Español (Spain)FrançaisItaliano (Italy)Português (Brasil)日本語Русский (Russia)中文 (简体) (China)中文 (繁體, 台灣) (Taiwan)ar-AR
  • Login

Learn about Identity Management

Default user identity (for backward compatibility)

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
Table of Contents
  • What is Identity Management?
    • What is Identity?
    • How OpenEdge supports user account systems
      • Authentication and user account systems
        • User accounts for OpenEdge-performed authentication
        • User accounts for ABL application-performed authentication
      • User credentials authenticated by OpenEdge
      • Specifying a user ID for OpenEdge authentication
      • Common authentication mechanism for database clients
    • OpenEdge identity types and their applications
      • Authenticated user identity
      • Default user identity (for backward compatibility)
        • ABL default identity constraints
        • SQL default identity constraints
        • Database utility default identity constraints
      • Authentication mechanisms for other OpenEdge components
    • User identity and multi-tenancy
  • How is OpenEdge Identity Managed?
    • OpenEdge authentication
      • Authentication operations
        • OpenEdge security systems and authentication
        • Authentication operations supported for OpenEdge security systems
      • User authentication process
        • Process for a user authentication operation
      • Single sign-on (SSO) process
        • Process for an SSO operation
        • Process for a successful SSO to an ABL session
        • Process for a successful SSO to an OpenEdge database connection
    • OpenEdge authorization
      • Tenant authorization
        • Tenancy data models
        • Managing tenancy access across multiple ABL sessions
      • Role-based authorization
  • Configuring and Implementing Authentication in OpenEdge
    • Defining and configuring security domains
      • Requirements to configure a domain
      • Defining the name of a domain
      • Defining and specifying the system type
        • OpenEdge support for user authentication and SSO
        • Specifying the system type
      • Entering a domain access code
      • Enabling and disabling domains
      • Entering system options
      • Identifying the tenant to which a domain belongs
      • Pre-configured and reserved OpenEdge domains
      • Configuring authentication-enabled domains
    • Configuring authentication
    • Run-time domain configuration
    • Entering user credentials in OpenEdge
    • Authentication in ABL applications
      • Initializing a client-principal object for user authentication
      • Exporting and importing a client-principal object
      • OpenEdge-performed authentication and SSO
      • Application-performed user authentication
      • Managing identity for multi-tenancy
        • Overview of Safe User ID
          • Programmatically use Safe User ID
          • Additional coding best practices
  • Configuring and Implementing Authorization in OpenEdge
    • OpenEdge authorization models
    • Non-multi-tenant vs. multi-tenant authorization
    • Tenant data access
    • When a user's domain is available for access control
    • User ID patterns as ACLs and ABL permissions checking
      • Patterns affecting ABL permissions
Table of Contents

Default user identity (for backward compatibility)

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
  • Last Updated: September 24, 2013
  • 1 minute read
    • OpenEdge
    • Version 13.0
    • Documentation

OpenEdge supports a default user identity that does not require authentication for database connections from ABL or the database utilities. OpenEdge does not normally support a default identity for SQL, but again, for backward compatibility, does allow OpenEdge SQL to be configured to accept a form of default identity.

Contents
  • ABL default identity constraints
  • SQL default identity constraints
  • Database utility default identity constraints
TitleResults for “How to create a CRG?”Also Available inAlert