Servlet Authentication Filters for Multi-Phase Web Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing security mechanisms for web applications, such as servlets, are limited in utilizing supplemental authentication mechanisms due to restrictions imposed by server containers, making it difficult to implement interactive authentication processes with clients or other servers.

Innovation Solution

The implementation of servlet authentication filters that can modify requests and session states to enable multi-phase authentication processes, allowing for the invocation of additional filters or external authentication providers, thereby extending the authentication capabilities beyond default mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom plug-in mechanisms for authentication are implemented on different servers, then authentication flexibility is improved, but integration with servlet containers becomes problematic and authentication is restricted to server container types

Engineering Contradiction:
Improveauthentication flexibilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces servlet authentication filters as an intermediary layer between the servlet container and external authentication providers. These filters intercept authentication requests, modify them as needed, and forward them to appropriate authentication mechanisms, thereby enabling integration of custom plug-in authentication without directly modifying the servlet container infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The authentication process is segmented into separate filter components that can be independently configured and deployed. Each filter handles specific authentication tasks, allowing the system to incorporate multiple authentication mechanisms without creating a monolithic complex integration structure.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If servlets are restricted to use only authentication types offered by the server container, then system simplicity is maintained, but authentication mechanism versatility is limited

Engineering Contradiction:
Improvesystem simplicityVSAvoidauthentication mechanism versatility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The servlet authentication filter framework provides a universal interface that can work with multiple types of authentication mechanisms. The filters are designed to handle various authentication protocols and providers through a common architecture, enabling servlets to access diverse authentication methods while maintaining a unified programming model.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

Authentication filters serve as mediators that translate between the servlet container's standard authentication interface and external authentication providers. This allows servlets to continue using simple container-provided authentication APIs while the filters handle the complexity of integrating with diverse external authentication systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7610613B2Servlet authentication filters
Publication Date: 2009.10.27 ORACLE INT CORP
  • US7610613B2 patent drawing
  • US7610613B2 patent drawing
  • US7610613B2 patent drawing

AI summary

In accordance with embodiments, one or more authentication filters may be employed to supplement an authentication process. The authentication process to be supplemented may be executed by one or more servlets in a servlet container. A servlet authentication filter is an authentication filter that may be invoked by a servlet. Requests may be made by requestors (also called “users”), which include humans as well as computational entities. The ability to modify a request and/or request state can enable multi-phase authentication processes, i.e., authentication processes with more than one authentication step, or modification to a default authentication process, i.e., authentication processes invoked if no other authentication processes are provided.