What is Instance-Level SSO?

Instance-level Single Sign-On (SSO) allows users to log in to their Neo4j database securely and retrieve data from a specific database. Each user can have different roles assigned, controlling access and actions within that database. This feature enhances security and simplifies user management.

Instance-level SSO can be configured in two ways:

---

1. Direct Configuration on the Aura Instance

In this method, SSO is configured directly on a specific Aura instance. This requires reaching out to the Aura Support team to request the configuration.

Steps to Configure:

1. Contact the Aura Support team via a support ticket.
2. Provide details about the instance and the SSO setup requirements.
3. Await confirmation from the support team once the configuration is complete.

Pros:

• Flexible role assignment: Each user can have unique roles tailored to the instance's requirements.
• Suitable for instances requiring granular role-based access control.

Cons:

• Manual process: Requires submitting a support ticket for each instance.
• Time-consuming for managing multiple instances.

---

2. Using Console/Organization SSO with Cascade to Projects Enabled

This method allows you to configure SSO at the organization level in the Aura Console and enable the "cascade to projects" feature. When cascade to projects is enabled, all new instances created within the project automatically inherit the instance-level SSO configuration.

Steps to Configure:

1. Access the Aura Console and configure Organization SSO.
2. Enable the Cascade to Projects option.
3. Create new instances within the project, which will automatically have SSO applied.

Pros:

• Streamlined setup: Configure once at the project level, and all new instances inherit the SSO configuration.
• Self-service: No need to submit support tickets for new instances.

Cons:

• Uniform role assignment: All instances within the project share the same role assignments.
  • To change roles for a specific instance, you need to contact the Aura Support team.
• Less flexible compared to direct configuration for individual instance role customizations.

---

Summary of Key Differences

Caption

Feature	Direct Configuration	Cascade to Projects
Setup Process	Requires support ticket	Configured via Aura Console
Role Assignment	Flexible, per-instance	Uniform across the project
Effort for Multiple Instances	High	Low

---

Recommendation:
Choose the configuration method based on your use case. For unique role requirements or existing instances, use direct configuration. For managing multiple instances with consistent settings, cascade to projects offers a more efficient approach.