Docs Developer Site
Enonic XP
arrow-down
  1. Manifesto
    1. Projects
    2. Build System
    1. Controllers
    2. Globals
    3. HTTP
    4. Localization
    5. Java bridge
    1. Architecture
    2. Asset service
    3. HTTP services
    4. Image service
    5. Component service
    1. NoQL syntax
    2. System properties
    3. Index configuration
    4. Aggregations
    5. Branches
  6. IAM
  7. Admin
    1. Schema System
    2. Mixins
    3. Input Types
    4. Content Types
    5. X-data
    6. Macros
    7. Sites
    8. Page Components
    9. Contributions
    10. Mappings
    11. Response Processors
    1. Distributions
    2. Vhosts
    3. Configuration
    1. Admin API
    2. Authentication API
    3. Cluster API
    4. Common API
    5. Content API
    6. Context API
    7. Event API
    8. I18N API
    9. IO API
    10. Mail API
    11. Node API
    12. Portal API
    13. Tasks API
    14. Value API
    15. Websocket API
    16. Management API
    17. Statistics API
    1. Upgrade Notes
    2. Upgrading Apps
DocIAM

Identity and access management (IAM)

Contents

Identity and access management (IAM)

Identity and access management (IAM)

Enonic XP ships with a clearly defined and pluggable concept for handling authentication and authorization

Introduction

Like a regular operating system, Enonic XP ships with a defined system for handling users, logins, roles based authorization as well as fine grained access control down to a single item in the NoSQL storage.

Principals

Users

A central concept in XP are users. Users consist of the following properties:

  • Username

  • key

  • e-mail

Groups

Groups are dynamically defined pri

Roles

As opposed to groups, roles are closely related to application specific functionality. For instance, a role typically

Identity providers

TODO

Vhost mapping

TODO

Contents