从Glassfish 4.0迁移到Glassfish 4.1.1-JDBC领域问题 [英] Migration from glassfish 4.0 to Glassfish 4.1.1 - JDBC Realm issue

问题描述

我在Glassfish domain.xml中具有此安全配置，该配置适用于4.0，但在4.1.1中失败，有人可以帮助您确定出什么问题了.唯一的区别是类包"ee"

I have this security configuration in Glassfish domain.xml which works for 4.0 but fail in 4.1.1 can someone help to identify what is wrong. The only difference is the class package "ee"

GF 4.0(带有额外的ee)

GF 4.0 (with extra ee)

<auth-realm classname="com.sun.enterprise.security.ee.auth.realm.jdbc.JDBCRealm" name="authentication-realm">
<property name="jaas-context" value="jdbcRealm"></property>
<property name="password-column" value="password"></property>
<property name="datasource-jndi" value="jdbc/SomeDS"></property>
<property name="group-table" value="v_user_role"></property>
<property name="charset" value="UTF-8"></property>
<property name="user-table" value="v_user_role"></property>
<property name="group-name-column" value="rolename"></property>
<property name="digest-algorithm" value="SHA-256"></property>
<property name="user-name-column" value="username"></property>
<property name="digestrealm-password-enc-algorithm" value="SHA-256"></property>
<property name="encoding" value="Base64"></property>
</auth-realm>

GF 4.1.1

<auth-realm classname="com.sun.enterprise.security.auth.realm.jdbc.JDBCRealm" name="authentication-realm">
<property name="jaas-context" value="jdbcRealm"></property>
<property name="password-column" value="password"></property>
<property name="datasource-jndi" value="jdbc/SomeDS"></property>
<property name="group-table" value="v_user_role"></property>
<property name="charset" value="UTF-8"></property>
<property name="user-table" value="v_user_role"></property>
<property name="group-name-column" value="rolename"></property>
<property name="digest-algorithm" value="SHA-256"></property>
<property name="user-name-column" value="username"></property>
<property name="digestrealm-password-enc-algorithm" value="SHA-256"></property>
<property name="encoding" value="Base64"></property>
</auth-realm>

推荐答案

发生此问题是因为我将JBDC资源从glassfish 4.0复制粘贴到glassfish 4.1.1 domain.xml.手动还原JDBC资源并使用管理控制台或命令行重新创建后，该问题已解决.

The problem happened because I copy-pasted the JBDC resource from glassfish 4.0 to glassfish 4.1.1 domain.xml. The problem was resolved after reverting the JDBC resource manually and re-create using admin console or command line.

这篇关于从Glassfish 4.0迁移到Glassfish 4.1.1-JDBC领域问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！