Security - User Manager

Manage administrator users, roles, and permissions

Overview

The User Manager provides per-user access control for the ColdFusion Administrator, the Administrator API and RDS. Instead of sharing a single administrator password among multiple team members, you can create individual user accounts with specific permissions tailored to each person's responsibilities.

This feature enables the principle of least privilege, improves accountability through audit trails, and eliminates the security risks associated with shared credentials.

Prerequisite: Users you create here can log in only after you select Separate Username And Password Authentication on the Security > Administrator page (and on the RDS page for RDS access). Source: Adobe: Use the ColdFusion Administrator

User Management

Create and manage individual administrator user accounts.

Creating Administrator Users

PurposeCreate individual accounts for each administrator
Required Info• Username (unique identifier)
• Password (strong, unique)
• Description (user's name/role)
• Assigned roles (permissions)
Best PracticeOne account per person - never share credentials
Username Guidelines:
  • Use real names or email addresses for accountability (e.g., "john.doe" or "jdoe@company.com")
  • Avoid generic names like "admin", "webmaster", "developer"
  • Use consistent naming convention across team
  • Document who each account belongs to
Security: Never create shared "team" accounts. Each administrator must have their own unique credentials for proper audit trails and accountability.

Password Requirements

Minimum Length12+ characters (16+ recommended)
ComplexityMix of uppercase, lowercase, numbers, and symbols
UniquenessDifferent from all other passwords user has
RotationChange every 90 days or when employee departs
Password Best Practices:
  • Use password manager to generate and store complex passwords
  • Never reuse passwords from other systems
  • Enforce password expiration policies
  • Lock accounts after multiple failed login attempts
  • Require password change on first login
  • Maintain password history to prevent reuse

User Account Lifecycle

OnboardingCreate account with minimal permissions, increase as needed
Active UseRegular access reviews, monitor for unusual activity
Role ChangesUpdate permissions when responsibilities change
OffboardingDisable account immediately when employee departs
Critical: Disable administrator accounts immediately when employees leave the company. Do not wait until next password rotation or access review.

Role-Based Access Control

Permissions are set per user. On each user's User Manager entry you select the Administrator pages (roles) the user can access, plus the options below.

Allowed Roles (Administrator Sections)

Select the ColdFusion Administrator pages, such as Data Sources or Mail, that the user can access.

Allowed Sandboxes

Select any sandboxes that the user can access.

Exposed Services

Choose which ColdFusion services exposed as web services (for example cfdocument, cfpdf, cfimage, cfmail, cfpop, cfchart and the upload service) the user may call. All are prohibited by default.

Console or API Access

Choose Administrator Console and API Access, or API Access Only for service accounts used by automation. A separate option allows RDS access.

Permission Types

Available Permission Categories

Administrator Sections:
  • Server Settings: Core server configuration, request handling, caching, mail
  • Data & Services: Datasources, web services, Solr
  • Debugging & Logging: Debug output, log files, monitoring
  • Extensions: Java applets, CFX tags, custom tag paths
  • Event Gateways: Gateway configuration and management
  • Security: Sandboxes, RDS, secure profile, user manager (if authorized)
  • Packaging & Deployment: CAR/EAR file operations
Example Least-Privilege User
USER: "dba.jsmith" (database team member)
==============================================

Allowed roles (Administrator sections):
  - Data Sources

Prohibited roles:
  - Every other section, including Security and User Manager

Allowed sandboxes:
  (none)

Exposed services:
  (none)

Access type:
  Administrator console and API access

Review schedule:
  Quarterly review to confirm the sections are still needed

Access Control Best Practices

Principle of Least Privilege

Implementation Guidelines:
  • Start with minimal permissions, add only what's needed
  • Grant access to specific sections, not full administrator
  • Use temporary privilege elevation for one-time tasks
  • Remove permissions when no longer required
  • Regular access reviews (quarterly minimum)
  • Document business justification for each permission

Separation of Duties

Role Segregation Examples:
  • Developer vs. Production Admin: Developers shouldn't have production write access
  • Security vs. Operations: Separate security policy management from daily operations
  • Database vs. Application: DBA manages datasources, app team manages code deployments
  • Monitoring vs. Configuration: Support can view logs but not change settings
Compliance: Many regulations (SOX, PCI-DSS, HIPAA) require separation of duties. Document your role structure for audit purposes.

User Account Auditing

Activity Loggingaudit.log records Administrator login/logout and update actions
Review FrequencyWeekly log review, quarterly access review
Anomaly DetectionMonitor for unusual login times, locations, or activity patterns
Audit Checklist:
  • Review all user accounts quarterly - disable unused accounts
  • Verify each user still requires their assigned permissions
  • Check for accounts of departed employees
  • Review recent administrator actions in logs
  • Verify no shared accounts exist
  • Confirm password rotation compliance
  • Check for failed login attempts (potential attacks)
  • Document all findings and remediation actions

Multi-Factor Authentication (MFA)

Enhanced Login Security

AvailabilityThe User Manager supports SAML and LDAP external users, so MFA can be enforced by your SAML identity provider. The Security section also documents client certificate authentication for Administrator access
RecommendationImplement MFA for all administrator accounts
Options• SAML SSO for the Administrator, with MFA enforced by the IdP
• LDAP/Active Directory external authentication
• VPN with MFA as access layer
• Custom authentication filters
MFA Implementation Approaches:
  • Network Level: Require VPN with MFA before accessing admin port
  • Web Server: Apache/IIS authentication modules with MFA
  • Directory Integration: LDAP/AD with built-in MFA support
  • Proxy/Gateway: Reverse proxy requiring MFA before CF admin

Integration with Enterprise Directory

LDAP / Active Directory Integration

Benefits• Centralized user management
• Single sign-on capability
• Automated account provisioning/deprovisioning
• Enterprise password policies enforced
ConfigurationIn Security > User Manager, click Add User and choose SAML or LDAP for an external user, then select the Administrator pages the user can access. SAML also uses the IDP configuration and SP configuration settings in the Security section
Best Practice: When using directory integration, disable local ColdFusion accounts except for emergency "break-glass" administrative account stored securely offline.
LDAP Integration Example
LDAP External Users
==========================================

1. Security > Administrator: select separate user name and
   password authentication
2. Security > User Manager > Add User: choose LDAP (or SAML)
   for the external user
3. Select only the Administrator pages the user needs

Benefits:
- User leaves company → directory account disabled → CF login fails
- Password policies → Managed centrally in the directory
- With SAML instead of LDAP, MFA is enforced by the IdP

Emergency Access:
  Local CF account: "emergency_admin"
  Stored in: Sealed envelope in safe
  Used for: Directory outage or emergency access
  Review: Quarterly password rotation

Common Issues & Solutions

User Cannot Login After Creation

Symptom: Newly created user gets "Invalid credentials" error when logging in
Solutions:
  • Verify username entered correctly (case-sensitive)
  • Confirm password meets complexity requirements
  • Confirm Security > Administrator is set to separate user name and password authentication
  • Verify user has at least one Administrator page allowed
  • Check for special characters in username/password
  • Review administrator logs for authentication errors

User Has No Access to Any Sections

Symptom: User can login but sees empty administrator or "Access Denied" errors
Solutions:
  • Verify the user has at least one Administrator page in the allowed roles list
  • Confirm the changes were saved with Edit User
  • Have the user log out and back in: role changes take effect only at the next login

Lost Administrator Access

Symptom: All administrator accounts locked or forgotten, cannot access admin
Recovery Steps:
  • Run the password reset utility in cfusion/bin (passwordreset.bat on Windows, passwordreset.sh on Linux, both shipped in ColdFusion 2025) as an administrator and follow its prompts
  • Restrict access to cfusion/lib/password.properties, which stores the Administrator password in encrypted form, and to the reset utility; Adobe lists both among files to protect (script name and file contents verified in the ColdFusion 2025 Update 14 files shipped in Adobe's official Docker image)
  • Restore from configuration backup if available
  • Contact Adobe Support with server license info
  • Document incident and update password management procedures

LDAP Integration Not Working

Symptom: Users cannot login with AD/LDAP credentials
Solutions:
  • Verify LDAP server connection (host, port, SSL)
  • Check LDAP bind credentials are correct
  • Confirm DN (Distinguished Name) format matches your directory
  • Test that an LDAP query returns the expected user
  • Confirm the user was added in User Manager as an LDAP user
  • Check firewall allows LDAP traffic (port 389 or 636 for SSL)
  • Review ColdFusion logs for LDAP connection errors
  • Test with LDAP browser tool to verify directory structure

Security Documentation Template

Administrator Access Documentation
COLDFUSION ADMINISTRATOR ACCESS CONTROL
========================================
Server: production-cf01.company.com
Last Updated: 2025-10-27
Owner: Infrastructure Team

ADMINISTRATOR USERS
-------------------
Username         | Name              | Allowed pages (roles)      | Created
-----------------|-------------------|----------------------------|-----------
john.doe         | John Doe          | All pages                  | 2024-01-15
jane.smith       | Jane Smith        | All pages                  | 2024-01-15
bob.jones        | Bob Jones         | Data Sources               | 2024-03-20
sarah.wilson     | Sarah Wilson      | Security pages             | 2024-06-10
mike.chen        | Mike Chen         | Logging pages              | 2024-08-15
emergency_admin  | Emergency Account | Root administrator         | 2024-01-15

PER-USER ACCESS NOTES
---------------------
For each user, record the allowed Administrator pages,
allowed sandboxes, exposed services, access type
(console and API, or API only) and RDS access, plus the
business reason for each.

ACCESS REVIEW LOG
------------------
Date       | Reviewer    | Actions Taken
-----------|-------------|-----------------------------------------------
2025-10-27 | Jane Smith  | Quarterly review - no changes needed
2025-07-15 | John Doe    | Removed tom.brown (departed employee)
2025-04-20 | Jane Smith  | Added mike.chen with logging pages only
2025-01-15 | John Doe    | Quarterly review - all accounts verified

EMERGENCY ACCESS PROCEDURES
----------------------------
Emergency Account: emergency_admin
Location: Sealed envelope in server room safe
Access Required: Two senior team members (dual control)
Usage: AD/LDAP outage or loss of all other administrator access
Post-Use: Change password immediately, document usage

INTEGRATION
-----------
Directory: Active Directory (ad.company.com)
Authentication: LDAP over SSL (port 636)
User setup: LDAP users added individually in User Manager
MFA: Required via VPN (Cisco AnyConnect + Duo)

NEXT REVIEW DUE
---------------
Date: 2026-01-27 (quarterly)
Responsible: Infrastructure Team Lead

Related Resources

Security - User Manager | ColdFusion Administrator | CFGuide