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

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 for

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

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 that it doesn't

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

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

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

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 (but not