In the previous screen, we selected the DB driver and specified the Data Source user and password.
在上一个屏幕中，我们选择了数据库驱动程序并指定了数据源用户和密码。
It contains information regarding your data source (DB URL, schema name, username, password, etc.) and references to other configuration files that will contain your mapping information.
它包含与数据源有关的信息(数据库url、模式名称、用户名、口令等)，以及对包含映射信息的其他配置文件的引用。
The sample code relies on passing user name and password to the JDBC driver and only if those credentials are successfully used to establish a DB connection the visa will be issued.
示例代码依赖于把用户名和密码传递给JDBC驱动程序，而且只有在使用这些凭证成功地建立DB连接的情况下，才会颁发visa。
Edit the file and enter the user name, password, and URL of your JRules RES db for the persistenceProperties property.
编辑文件并针对 persistenceProperties属性输入JRulesRESdb的用户名、密码和URL。
To establish a database connection, select DB name, userID, password, DB2 Universal Database 8.1, and take all defaults for the remaining options.
要建立数据库连接，可以选择DBname,userID,password,DB2UniversalDatabase 8.1，然后接受剩余选项的所有缺省值。
The connection URL, username, and password are also the same as what you entered in the my-db-plan.xml file in Part 1.
连接url、用户名和口令也都与在第1部分的my - db - plan. xml文件中输入的相同。
Comparing the high security for password storage and pretty dump idea of string private and public key directly in DB, I feel a much greated gap between those two security levels.
比较密码存储的高安全性和字符串私有和公共密钥的漂亮转储想法直接在DB中，我觉得这两个安全级别之间有很大的差距。
The weird result is that I found the CONFIGURATIONS table updated with the password plaintext in the db!
奇怪的是，我发现CONFIGURATIONS表更新在数据库中的密码明文！
The weird result is that I found the CONFIGURATIONS table updated with the password plaintext in the db!
奇怪的是，我发现CONFIGURATIONS表更新在数据库中的密码明文！
应用推荐