Re: Absolute fields required for JDBC & JNDI Realm pages in adminwebapp

2002-08-16 Thread Amy Roh
John Holman wrote: > Amy Roh wrote: > >> I just committed fixes to validate only className and connectionURL >> and also to >> check either userPattern or userSearch is specified but not both. > > > Thanks! > >> I don't think any change to JNDIRealm is necessary since I changed >> admin so t

Re: Absolute fields required for JDBC & JNDI Realm pages in adminwebapp

2002-08-16 Thread John Holman
Amy Roh wrote: > I just committed fixes to validate only className and connectionURL and also to > check either userPattern or userSearch is specified but not both. Thanks! > I don't think any change to JNDIRealm is necessary since I changed admin so that > it doesn't replace null values with "

Re: Absolute fields required for JDBC & JNDI Realm pages in adminwebapp

2002-08-15 Thread Amy Roh
John, Thanks for the feedback. John Holman wrote: > Amy > > Yes - much too strict for JNDIRealm! I agree! > The only configuration attributes > that should always be specified for this realm are className and > connectionURL. In addition either userPattern or userSearch must be > specified (b

Re: Absolute fields required for JDBC & JNDI Realm pages in adminwebapp

2002-08-15 Thread John Holman
Amy Yes - much too strict for JNDIRealm! The only configuration attributes that should always be specified for this realm are className and connectionURL. In addition either userPattern or userSearch must be specified (but not both). Other attributes either have default values, or not specify