slocumbf / owasp-esapi-java

Automatically exported from code.google.com/p/owasp-esapi-java
0 stars 0 forks source link

Unit test org.owasp.esapi.UserTest throws InvalidAccountName Exception #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Brought up Project under Eclipse 3.3 using Java 1.6
2. Added "test" directory as a source directory.
3. Added VM argument 
    -Dorg.owasp.esapi.resources="/owasp/test/testresources"
4. The UserTest unit tests report an error: 
org.owasp.esapi.errors.AuthenticationCredentialsException: Invalid 
account name
    at org.owasp.esapi.Authenticator.verifyAccountNameStrength
(Authenticator.java:653)
    at org.owasp.esapi.User.<init>(User.java:190)
    at org.owasp.esapi.Authenticator.createUser
(Authenticator.java:237)
(the rest deleted)...       

What is the expected output? What do you see instead?
Expected a "passed" or "failed"

What version of the product are you using? On what operating system?
Product Version: ESAPI v1.1.1 Complete JAR file
OS: Windows XP
Java: 1.6 update 5

Original issue reported on code.google.com by robert.m...@gmail.com on 7 Apr 2008 at 5:14

GoogleCodeExporter commented 9 years ago
I changed the -D option to use an absolute path and that fixed this issue.

Original comment by robert.m...@gmail.com on 7 Apr 2008 at 5:28

GoogleCodeExporter commented 9 years ago
The resource path mechanism has been updated to use the classpath, and then as 
a 
backup, the -D environment variable is used.

Original comment by planetlevel on 31 Aug 2008 at 12:24