SOAPatterns.org

Overview
- Introduction
- History
- Acknowledgements
- Podcasts
- Candidate Patterns
- Forms
- Press Releases
- Resources
Compound Patterns
Design Patterns (alphabetical)
Design Patterns (by category)
- Foundational Inventory Patterns
- Logical Inventory Layer Patterns
- Inventory Centralization Patterns
- Inventory Implementation Patterns
- Inventory Governance Patterns
- Foundational Service Patterns
- Service Implementation Patterns
- Service Security Patterns
- Service Contract Design Patterns
- Legacy Encapsulation Patterns
- Service Governance Patterns
- Capability Composition Patterns
  - Capability Composition
  - Capability Recomposition
- Service Messaging Patterns
- Composition Implementation Patterns
- Service Interaction Security Patterns
- Transformation Patterns
- REST-inspired Patterns
Cloud Computing Patterns
Service Technology Specs
SOA School
- Home
- Matrix
- Certifications
- Courses
- Exams
- Self-Study Kits
- Workshops
- Licensing
- Online Store

Home > Design Patterns > Trusted Subsystem

Trusted Subsystem (Hogg, Smith, Chong, Hollander, Kozaczynski, Brader, Delgado, Taylor, Wall, Slater, Imran, Cibraro, Cunningham)

How can a consumer be prevented from circumventing a service and directly accessing its resources?

Problem

A consumer that accesses backend resources of a service directly can compromise the integrity of the resources and can further lead to undesirable forms of implementation coupling.

Solution

The service is designed to use its own credentials for authentication and authorization with backend resources on behalf of consumers.

Application

Depending on the nature of the underlying resources, various design options and security technologies can be applied.

Impacts

If this type of service is compromised by attackers or unauthorized consumers, it can be exploited to gain access to a wide range of downstream resources.

Principles

Service Loose Coupling

Architecture

Service

Neither a malicious or non-malicious consumer can access the database directly. Only the service itself can access the database with its own credentials.

Related Patterns in This Catalog

Brokered Authentication, Direct Authentication

Related Service-Oriented Computing Goals

Increased Intrinsic Interoperability, Reduced IT Burden

This page contains excerpts from:

SOA Design Patterns by Thomas Erl

Foreword by Grady Booch

With contributions from David Chappell, Jason Hogg, Anish Karmarkar, Mark Little, David Orchard, Satadru Roy, Thomas Rischbeck, Arnaud Simon, Clemens Utschig, Dennis Wisnosky, and others.

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit www.servicetechbooks.com.