Identity & Enterprise Integration

Fit platform access into the controls your enterprise already uses.

Enterprise adoption requires the platform to operate within established identity, access, security, and governance expectations.

Access paths that get validated
User accessenterprise identity provider, organizational roles
Administrator accesselevated permissions with explicit responsibility
Integration accessconnector authorization to connected repositories and systems
Platform access should look like the rest of your enterprise access.
Overview

Platform access should look like the rest of your enterprise access.

Identity & Enterprise Integration defines and implements the supported connections between Applied SAFe® Platform and the customer's enterprise identity and access environment.

Objective

Establish secure and manageable access to the platform that aligns with the customer's enterprise controls.

Service scope can include

Identity, access, and the boundaries between them.

  • User identity
  • Authentication
  • Administrator access
  • Authorization concepts
  • Organizational roles
  • Enterprise identity-provider integration
  • Access boundaries
  • Connector authorization
  • Environment separation
  • Enterprise security requirements
How the service works

Five steps from enterprise requirements to validated access.

  1. Understand enterprise requirements

    Review the customer's identity, access, and security expectations relevant to the platform.

  2. Map platform roles and access

    Determine how platform access maps to organizational responsibilities.

  3. Configure supported identity integration

    Implement the appropriate supported authentication and enterprise integration model.

  4. Configure connector authorization

    Establish access for connected repositories and systems using the required enterprise mechanisms.

  5. Validate access scenarios

    Test representative user, administrator, and integration access paths.

Deliverables
  • Identity and access design
  • Platform-role mappings
  • Configured supported integrations
  • Connector authorization model
  • Validation results
  • Administration guidance
Benefits
  • Use the identity controls the enterprise already operates.
  • Map platform access to real organizational responsibility.
  • Make connector authorization explicit rather than incidental.
  • Validate the access paths that actually get used.
Often paired with
Enterprise & Private Deployment

Identity and deployment constraints are usually decided together.

Connect platform access to the enterprise controls around it.