How to log-in?

Hi

 

My initial email was sent before I was accepted to the subscriber list for
JAMM, so here is additional information.

 

I'm running Trustix Server Linux 2.1 and I've just installed OpenLDAP
2.1.25-3 from the distribution together with Jamm-0.9.6, j2sdk1.4.2_04 and
tomcat.  I've followed the instructions in the HOWTO and I've got JAMM
running via Tomcat.  Now, when I go to the login page I'm being asked for a
userid and password.  What values should I be entering here?  I've tried
Manager with the rootdn password but this is rejected.  Have I missed a step
out?  Help please!

 

Here is my slapd.conf:

 

# $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.23.2.7 2003/03/24
03:54:12 kurt Exp $

#

# See slapd.conf(5) for details on configuration options.

# This file should NOT be world readable.

#

include                        /etc/openldap/schema/core.schema

 

# The following schemas are included in the package:

#include          /etc/openldap/schema/corba.schema

include            /etc/openldap/schema/cosine.schema

#include          /etc/openldap/schema/inetorgperson.schema

#include          /etc/openldap/schema/java.schema

#include          /etc/openldap/schema/misc.schema

include            /etc/openldap/schema/nis.schema

#include          /etc/openldap/schema/openldap.schema

include /etc/openldap/schema/jamm.schema

 

# Define global ACLs to disable default read access.

 

# Do not enable referrals until AFTER you have a working directory

# service AND an understanding of referrals.

#referral          ldap://root.openldap.org

 

pidfile              /var/run/slapd.pid

argsfile           /var/run/slapd.args

 

# Load dynamic backend modules:

# modulepath             /usr/lib

# moduleload back_ldbm.la

# moduleload back_ldap.la

# moduleload back_ldbm.la

# moduleload back_passwd.la

# moduleload back_shell.la

 

 

##################################################################

# Sample security restrictions

##################################################################

#

#   Disallow clear text exchange of passwords

# disallow bind_simple_unprotected

#

#          Require integrity protection (prevent hijacking)

#          Require 112-bit (3DES or better) encryption for updates

#          Require 63-bit encryption for simple bind

# security ssf=1 update_ssf=112 simple_bind=64

 

# Sample access control policy:

#          Root DSE: allow anyone to read it

#          Subschema (sub)entry DSE: allow anyone to read it

#          Other DSEs:

#                      Allow self write access

#                      Allow authenticated users read access

#                      Allow anonymous users to authenticate

#          Directives needed to implement policy:

# access to dn.base="" by * read

# access to dn.base="cn=Subschema" by * read

# access to *

#          by self write

#          by users read

#          by anonymous auth

#

# if no access controls are present, the default policy is:

#          Allow read by all

#

# rootdn can always write!

access to dn=".*,jvd=([^,]+),o=hosting,dc=rvw,dc=sytes,dc=net"

               attr=userPassword

            by self write

            by
group/jammPostmaster/roleOccupant="cn=postmaster,jvd=$1,o=hosting,dc=rvw,dc=
sytes,dc=net" write

            by anonymous auth

            by * none

 

access to dn=".*,jvd=([^,]+),o=hosting,dc=rvw,dc=sytes,dc=net"

            by self write

            by
group/jammPostmaster/roleOccupant="cn=postmaster,jvd=$1,o=hosting,dc=rvw,dc=
sytes,dc=net" write

            by * read

 

access to *

            by * read

 

#################################################################

# Sample TLS configuration (self signed certificate)

#################################################################

 

#TLSCertificateFile    /etc/openldap/my-domain.crt

#TLSCertificateKeyFile /etc/openldap/my-domain.key

#TLSCACertificateFile  /etc/openldap/my-domain.crt

#TLSChiperSuite HIGH

#TLSVerifyClient never

 

 

 

#######################################################################

# database definitions

#######################################################################

 

database        ldbm

suffix               "dc=rvw,dc=sytes,dc=net"

rootdn             "cn=Manager,dc=rvw,dc=sytes,dc=net"

# Cleartext passwords, especially for the rootdn, should

# be avoided.  See slappasswd(8) and slapd.conf(5) for details.

# Use of strong authentication encouraged.

 

# A rootdn password is required. The following lines are examples, do not 

# use the passwords provided here.

 

# rootpw                     secret

# rootpw                                 myC5llo

# rootpw                    {SSHA}Lu1m6z4FzVgJoMsSCcLZq9rdaRNxlQQd

# rootpw
{SSHA}KNf5SrucrIeo/UG6mzMIk6Kt81xrriOd

 

# The database directory MUST exist prior to running slapd AND 

# should only be accessible by the slapd and slap tools.

# Mode 700 recommended.

directory         /var/lib/openldap        

# Indices to maintain

index   objectClass    pres,eq

index   mail,cn                        eq,sub

# rootpw {SSHA}z2YKn95SXyZPdeEq/JmegFtRSiHrCwAo

rootpw {SSHA}bEJWR4t8uFSP4EQv/cY10IRrtQzV4OWV

 

Here is my jamm.properties:

 

 

# The LDAP host.  The default is localhost

#

jamm.ldap.host = 192.168.0.200

 

# The LDAP port. The default is 389

#

#jamm.ldap.port =

 

# The search base.

#

jamm.ldap.search_base  = o=hosting,dc=rvw,dc=sytes,dc=net

 

# The DN of the "root" user

#

jamm.ldap.root_dn = cn=Manager,dc=rvw,dc=sytes,dc=net

 

# The login of the "root" user.  The default is root

#

jamm.ldap.root_login = root

 

# The class used to generate random numbers.  The default is

# java.security.SecureRandom.

#

#jamm.random_class = java.util.Random

 

# Should jamm use the Modify Password Extended Operation to set the

# users's password?  If true, it will.  If false, jamm itself will

# generate an SSHA hash and set the userPassword attribute to it.

# The default is true

#

#jamm.password.exop = true

 

# The directory on the server where the virtual accounts store their

# data.  Defaults to /home/vmail/domains

#

#jamm.vmail.homedir = /home/vmail/domains

 

I added a few items to the ldap data base using part of the sample.ldif file
that came with JAMM.  Here's the output from an ldapsearch:

 

# extended LDIF

#

# LDAPv3

# base <dc=rvw,dc=sytes,dc=net> with scope sub

# filter: (objectClass=*)

# requesting: ALL

#

 

# rvw.sytes.net

dn: dc=rvw,dc=sytes,dc=net

objectClass: top

objectClass: domain

dc: rvw

 

# Manager, rvw.sytes.net

dn: cn=Manager,dc=rvw,dc=sytes,dc=net

objectClass: top

objectClass: organizationalRole

cn: Manager

 

# hosting, rvw.sytes.net

dn: o=hosting,dc=rvw,dc=sytes,dc=net

objectClass: top

objectClass: organization

o: hosting

 

# info.test, hosting, rvw.sytes.net

dn: jvd=info.test,o=hosting,dc=rvw,dc=sytes,dc=net

objectClass: top

objectClass: JammVirtualDomain

editAccounts: TRUE

postfixTransport: virtual:

lastChange: 1044310841

editPostmasters: TRUE

jvd: info.test

delete: FALSE

accountActive: TRUE

 

# postmaster, info.test, hosting, rvw.sytes.net

dn: cn=postmaster,jvd=info.test,o=hosting,dc=rvw,dc=sytes,dc=net

objectClass: top

objectClass: JammPostmaster

objectClass: JammMailAlias

mail: [email protected]

roleOccupant: cn=postmaster,jvd=info.test,o=hosting,dc=example,dc=com

lastChange: 1044310841

maildrop: postmaster

accountActive: TRUE

cn: postmaster

 

# [email protected], info.test, hosting, rvw.sytes.net

dn: [email protected],jvd=info.test,o=hosting,dc=rvw,dc=sytes,dc=net

objectClass: top

objectClass: JammMailAlias

mail: [email protected]

lastChange: 1044310841

maildrop: postmaster

accountActive: TRUE

 

# [email protected], info.test, hosting, rvw.sytes.net

dn: [email protected],jvd=info.test,o=hosting,dc=rvw,dc=sytes,dc=net

objectClass: top

objectClass: JammMailAccount

mail: [email protected]

lastChange: 1044310961

homeDirectory: /home/vmail/domains

mailbox: info.test/dave/

delete: FALSE

accountActive: TRUE

 

# search result

search: 2

result: 0 Success

 

# numResponses: 8

# numEntries: 7

 

I've tried to double-check everything, but I still can't log-in at the JAMM
screen on my browser because the username and password don't match.  But I'm
using Manager and my rootdn password.  I know the password is correct
because it is accepted by the ldap utilities such as ldapadd.

 

All ideas on solving this problem are appreciated.

 

Regards

 

Richard Williams

 

**************************************************** 
Richard Williams 
email: [email protected] 
****************************************************