To update the status of my problem, I've now tried a number of different 
field names, made sure of the case, and traced the SQL on the database. 
When I try to log in, I see from the server:

SELECT * FROM empuser WHERE NAME= 'ger'

which obtains correct row with my password (name field is called NAME and 
password field is called PWD). So now the question is why is Orion not 
thinking that I have not logged in if it's found the right record in the 
database? I've made sure that the group is called "players" and the role is 
called "players". I'm uncertain as to how I should proceed.

Any help would be greatly appreciated.

Thanks.



At 04:55 PM 11/14/2000 -0800, Gerald Gutierrez wrote:

>People have indicated success with this user manager but I cannot seem to 
>get it to work. I would appreciate some input those who have gotten it to work.
>
>I have the following in my orion-application.xml:
>
>     <security-role-mapping name="players">
>         <group name="players"/>
>     </security-role-mapping>
>
>     <user-manager class="com.evermind.sql.DataSourceUserManager">
>         <property name="dataSource" value="jdbc/MyDS"/>
>         <property name="table" value="EMPUSER"/>
>         <property name="usernameField" value="U"/>
>         <property name="passwordField" value="P"/>
>         <property name="defaultGroups" value="players"/>
>     </user-manager>
>
>I don't have the principals tag in the xml file. The table I use for 
>usernames and passwords is EMPUSER, and the fields are U and P. The role 
>that users should be using is "players". I'm quite sure that my dataSource 
>is set up properly because I use the same data source to do CMP table creation.
>
>I'm using Hypersonic (in client/server mode) as the database, which has 
>the EMPUSER table and a row containing ('ger', 'reg'), the username (U 
>column) and password (P column) respectively. I assume the password field 
>stores a plaintext password. For the actual authentication, I'm using the 
>"BASIC" method.
>
>No matter what I do, it does not seem to authenticate properly, and 
>ultimately the browser comes back as "unauthorized".
>
>What did I miss?



Reply via email to