Borland VisiBroker® 7.0 - Borland Technical Publications

Borland LoginModulesThe elements in square brackets (“[ .. ]”) are used only if authenticating to the TomcatRealm, where they would be required. Otherwise, the remaining properties aresufficient.PropertyDRIVERURLTYPELOGINUSERIDLOGINPASSWORD[USERTABLE][USERNAMEFIELDINUSER-TABLE][USERNAMEFIELDIN-GROUPTABLE][PASSWORDFIELD][GROUPTABLE][GROUPNAMEFIELD][DIGEST]DescriptionFully-qualified class name of the database driver tobe used with the password backend. For example,com.borland.datastore.jdbc.DataStoreDriverFully-qualified URL of the database used for therealm.The schema to use for this realm. This LoginModulesupports the schema used by the Tomcat JDBCrealm and can be made to use that schema. Set thisto “TOMCAT” to use the Tomcat schema. Set this to“basic” to use the Borland schema.Note: If this property is set to “TOMCAT,” all otherproperties in square braces (“[..]”) must also be set.Username needed to access the password backenddatabase.Password needed to access the password backenddatabase.Table name under which the username/password tobe authenticated is stored.The field name in USERTABLE where the userIDcan be read.The field name in GROUPTABLE where the userIDcan be read, different from that in the USERTABLE.The field name in USERTABLE containing thepassword for the username to be authenticated.Table name under where the group information forthe user is stored. When TYPE is set to “TOMCAT,”the attribute represented by entries in this table aretreated as roles rather than groups.Name of the field in GROUPTABLE containing thegroup name to be associated with the user. WhenTYPE is set to “TOMCAT,” the attribute representedby entries in this table are treated as roles ratherthan groups.The algorithm to use for digesting the password. Thisdefaults to SHA under basic circumstances, butdefaults to MD5 when TYPE is set to “TOMCAT”.Premium {com.borland.security.provider.authn.BasicLoginModule requiredDRIVER="com.borland.datastore.jdbc.DataStoreDriver"URL="jdbc:borland:dslocal:/Security/java/prod/userauthinfo1.jds"Realm="Basic"LOGINUSERID="CreateTx"LOGINPASSWORD="";};Since password should never be stored in clear text, VisiSecure always performsdigest on the password and stores the result into database. The digesttype optiondefines the digest algorithm for this. By default, an SHA algorithm is used for basictypedschema, while MD5 is used for tomcat-typed schema. You can change it byincluding and setting a digesttype option. In the case the corresponding digest typeengine cannot be found by the JVM, SHA is used instead. If an SHA engine cannot befound either, the authentication will always fail.Chapter 3: Authentication 33