[
https://issues.apache.org/jira/browse/JS2-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Kumar resolved JS2-749.
-----------------------------
Resolution: Won't Fix
We have tested this bug in different platform and scenario, this seems to be an
issue while loading jaas configuration file from java or tomcat. I have even
opened issue with tomcat for there response on this
(https://issues.apache.org/bugzilla/show_bug.cgi?id=45975)
I am marking this issue resolved, as in default setup of jetspeed-2, we
packaged our jaas configuration file in jar. This is current work around for
loading jaas configuration,if you have installed tomcat in directory which
have spaces.
> Jetspeed Login Module fails to load on Windows in directories with spaces in
> the path
> -------------------------------------------------------------------------------------
>
> Key: JS2-749
> URL: https://issues.apache.org/jira/browse/JS2-749
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Security
> Affects Versions: 2.2
> Environment: Windows
> Reporter: David Sean Taylor
> Assignee: Vivek Kumar
> Priority: Minor
> Fix For: 2.2
>
>
> Jetspeed Login Module fails to load on Windows in directories with spaces in
> the path
> It appears that we are breaking the Login Module on Windows when there are
> spaces in the path to the login module configuration file that Jetspeed
> provides, and is put into the work area of the application server. The
> problem is the Java class loader encodes the space, but then the file system
> does not understand the encoding (%20). If we do not encode the space, the
> file system correctly finds the resource. This change should be tested on all
> major file systems before committing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
