<%-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --%> <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %> <%@ taglib uri="http://java.sun.com/jsp/jstl/functions" prefix="fn" %> <%@ taglib uri="http://java.sun.com/portlet" prefix="portlet"%>

This page edits a new or existing security realm.

A security realm may have one or more login modules. Many simple realms have only one login module. Additional login modules may be used to access more underlying security information stores, or to add functionality such as auditing to a realm without affecting the authentication process for the realm.

If you don't need to use as many login modules as there are entries below, just leave the extra ones blank.
Realm Name:
 <%-- Can't change the realm name after deployment because it's wired into all the abstractNames --%>
A name that is different than the name for any other security realms in the server (no spaces in the name please). Other components will use this name to refer to the security realm.
Login Module JAR:
The jar containing Login Module and Principal classes.
Login Module ${status.index+1}
Login Domain Name:
 <%-- Can't change the login domain name after deployment because it's how we know which GBean is which --%>
The login domain for this login module, which must be unique among all modules in the security realm. This can be used to distinguish principals from two otherwise identical login modules (for example, from two LDAP login modules pointing to two different LDAP servers)
Login Module Class:
The fully-qualified class name for the login module.
Control Flag:
The control flag for the login module, which controls what happens to the overall login processing if this login module succeeds or fails. For more information see javax.security.auth.login.Configuration.
Server-Side:
Server-side login modules are executed within the application server (this is normally correct). Client-side login modules are executed in the client's environment, for example, in order to use single sign-on features of the client OS.
Support Advanced Mapping:
Normally Geronimo can't distinguish between two different principals that have the same name and same principal class but were produced by two different login modules. If this option is enabled, Geronimo will "wrap" principals to track which login module and realm each principal came from. This lets you use the "realm-principal" and "login-domain-principal" elements in your security mapping in Geronimo deployment plans.
Configuration Options:
Any configuration options necessary for the login module, in the standard Java properties format (one per line, name=value)
DeploySave" onclick="document.RealmForm.mode.value='save';document.RealmForm.submit();return false;" />

">Cancel