archive-es.com » ES » E » EPPA.ES

Total: 100

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Catalina Functional Specifications (7.0.22) - JNDIRealm
    or in one of the digested modes supported by the org apache catalina realm RealmBase base class For Username Login mode JNDIRealm does not normally remain connected to the directory server Instead whenever a user is to be authenticated a connection to the directory server using the username and password received from the authenticator is attempted If this connection is successful the user is assumed to be successfully authenticated This connection is then utilized to read the corresponding security roles associated with this user and the connection is then broken NOTE Username Login mode cannot be used if you have selected login method DIGEST in your web application deployment descriptor web xml file This restriction exists because the cleartext password is never available to the container so it is not possible to bind to the directory server using the user s username and password Because these operational modes work so differently the functionality for each mode will be described separately Whether or not both modes are actually supported by a single class versus a class per mode is an implementation detail left to the designer NOTE The current implementation only implements part of the Administrator Lookup mode requirements It does not support the Username Lookup mode at all at this point Administrator Login Mode Functionality Configurable Properties The implementation shall support the following properties that can be configured with JavaBeans property setters connectionURL URL of the directory server we will be contacting contextFactory Fully qualified class name of the JNDI context factory used to retrieve our InitialContext com sun jndi ldap LdapCtxFactory Additional configuration properties required to establish the appropriate connection Requested Connection pool configuration properties Requested Configuration properties defining how a particular user is authenticated The following capabilities should be supported Substitute the specified username into a string Requested Retrieve the distinguished name DN of an authorized user via an LDAP search string with a replacement placeholder for the username and comparison of the password to a configurable attribute retrieved from the search result Current Configuration properties defining how the roles associated with a particular authenticated user can be retrieved The following approaches should be supported Retrieve a specified attribute possibly multi valued from an LDAP search expression with a replacement placeholder for the DN of the user Current Retrieve a set of role names that are defined implicitly by selecting principals that match a search pattern rather than explicitly by finding a particular attribute value Requested Lifecycle Functionality The following processing must be performed when the start method is called Establish a connection to the configured directory server using the configured system administrator username and password Current Configure and establish a connection pool of connections to the directory server Requested The following processing must be performed when the stop method is called Close any opened connections to the directory server Method authenticate Functionality When authenticate is called the following processing is required Acquire the one and only connection Current or acquire a connection from the connection pool Requested

    Original URL path: http://ticket.eppa.es/docs/funcspecs/fs-jndi-realm.html (2015-09-25)
    Open archived version from archive


  • Catalina Functional Specifications (7.0.22) - MemoryRealm
    BASE conf server xml in a Realm element that is nested inside a corresponding Engine Host or Context element This is already included in the default server xml file Container Dependencies Correct operation of MemoryRealm depends on the following specific features of the surrounding container Interactions with MemoryRealm will be initiated by the appropriate Authenticator implementation based on the login method that is selected MemoryRealm must have an XML parser compatible with the JAXP 1 1 APIs available to it This is normally accomplished by placing the corresponding JAR files in directory CATALINA HOME lib Functionality Overview of Operation The main purpose of MemoryRealm is to allow Catalina to authenticate users and look up the corresponding security roles from the information found in an XML format configuration file The format of this file is described below When a MemoryRealm instance is started it will read the contents of this XML file and create an in memory database of all the valid users and their associated security roles Each time that Catalina needs to authenticate a user it will call the authenticate method of this Realm implementation passing the username and password that were specified by the user If we find the user in the database and match on the password we accumulate all of the security roles that are defined for this user and create a new GenericPrincipal object to be returned If the user is not authenticated we return null instead The GenericUser object caches the set of security roles that were owned by this user at the time of authentication so that calls to isUserInRole can be answered without going back to the database every time Detailed Functional Requirements Configurable Properties The implementation shall support the following properties that can be configured with JavaBeans property setters Configurable debugging

    Original URL path: http://ticket.eppa.es/docs/funcspecs/fs-memory-realm.html (2015-09-25)
    Open archived version from archive

  • Apache Tribes - The Tomcat Cluster Communication Module (7.0.22) - Apache Tribes - Configuration
    Sep 27 2011 Links Docs Home FAQ User Guide 1 Introduction 2 Setup 3 FAQ Reference JavaDoc Apache Tribes Development Membership Transport Interceptors Status Developers Apache Tribes Configuration Configuration Overview

    Original URL path: http://ticket.eppa.es/docs/tribes/setup.html (2015-09-25)
    Open archived version from archive

  • Apache Tribes - The Tomcat Cluster Communication Module (7.0.22) - Apache Tribes - Frequently Asked Questions
    27 2011 Links Docs Home FAQ User Guide 1 Introduction 2 Setup 3 FAQ Reference JavaDoc Apache Tribes Development Membership Transport Interceptors Status Developers Apache Tribes Frequently Asked Questions Frequently

    Original URL path: http://ticket.eppa.es/docs/tribes/faq.html (2015-09-25)
    Open archived version from archive

  • Apache Tribes - The Tomcat Cluster Communication Module (7.0.22) - Apache Tribes - Membership
    22 Sep 27 2011 Links Docs Home FAQ User Guide 1 Introduction 2 Setup 3 FAQ Reference JavaDoc Apache Tribes Development Membership Transport Interceptors Status Developers Apache Tribes Membership Membership

    Original URL path: http://ticket.eppa.es/docs/tribes/membership.html (2015-09-25)
    Open archived version from archive

  • Apache Tribes - The Tomcat Cluster Communication Module (7.0.22) - Apache Tribes - Transport
    22 Sep 27 2011 Links Docs Home FAQ User Guide 1 Introduction 2 Setup 3 FAQ Reference JavaDoc Apache Tribes Development Membership Transport Interceptors Status Developers Apache Tribes Transport Transport

    Original URL path: http://ticket.eppa.es/docs/tribes/transport.html (2015-09-25)
    Open archived version from archive

  • Apache Tribes - The Tomcat Cluster Communication Module (7.0.22) - Apache Tribes - Interceptors
    22 Sep 27 2011 Links Docs Home FAQ User Guide 1 Introduction 2 Setup 3 FAQ Reference JavaDoc Apache Tribes Development Membership Transport Interceptors Status Developers Apache Tribes Interceptors Interceptors

    Original URL path: http://ticket.eppa.es/docs/tribes/interceptors.html (2015-09-25)
    Open archived version from archive

  • Apache Tribes - The Tomcat Cluster Communication Module (7.0.22) - Apache Tribes - Status
    22 Sep 27 2011 Links Docs Home FAQ User Guide 1 Introduction 2 Setup 3 FAQ Reference JavaDoc Apache Tribes Development Membership Transport Interceptors Status Developers Apache Tribes Status Status

    Original URL path: http://ticket.eppa.es/docs/tribes/status.html (2015-09-25)
    Open archived version from archive