[jira] Commented: (JS2-749) Jetspeed Login Module fails to load on Windows in directories with spaces in the path

["Ate Douma (JIRA)" <je...@portals.apache.org>]

    [ https://issues.apache.org/jira/browse/JS2-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635603#action_12635603 ] 

Ate Douma commented on JS2-749:
-------------------------------

Aaron Evans provided a solution on the jetspeed-user list which we maybe can to solve it for the default provided login.conf too:
(note, I didn't test this myself yet)

Aaron Evans wrote:
> Ok, I figured out a solution to this (that is, how to configure your
> custom Login Module even if your tomcat is installed to a path with
> spaces).
> 
> What you can do is put your login.conf file in a jar file that you
> install in jetspeed/WEB-INF/lib.
> 
> So say you put the file under a package like com.mycompany.security.impl.
> 
> Then in security-providers.xml, configure the "location" of your
> login.conf to be:
> 
> com/mycompany/security/impl/login.conf
> 
> The file URL with the absolute path will then get constructed
> correctly and your login module will be found.
> 
> The URL will actually end up being something like:
> 
> file:${CATALINA_HOME}/work/Catalina/localhost/jetspeed/loader/com/mycompany/security/impl/login.conf
> 
> Where ${CATALINA_HOME} is the absolute path to your tomcat installation.
> 
> -aaron
>  

> 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: David Sean Taylor
>             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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org