You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Dinesh Premalal (JIRA)" <ji...@apache.org> on 2007/05/06 11:58:15 UTC

[jira] Created: (AXIS2C-601) Rampart Sample is Unable to pickup outgoing policy file

Rampart Sample is Unable to pickup outgoing policy file
-------------------------------------------------------

                 Key: AXIS2C-601
                 URL: https://issues.apache.org/jira/browse/AXIS2C-601
             Project: Axis2-C
          Issue Type: Bug
          Components: rampart
    Affects Versions: 0.96, Current (Nightly)
            Reporter: Dinesh Premalal


After building rampart , I tried to run samples but they failed. Although my environmental variables of

AXIS2C_HOME=/home/dinesh/axis2c/deploy
CLIENT_REPO=$AXIS2C_HOME/client_repo

log complains saying 

[rampart][rampart_Engine] Trying to build rampart context from file /home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml 
[Sun May  6 15:28:53 2007] [info]  [rampart][rampart_Engine] Cannot get policy
[Sun May  6 15:28:53 2007] [info]  [rampart][mod_rampart] mod_rampart shutdown

I have no idea where this path "home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml" came from ???


-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Re: [jira] Created: (AXIS2C-601) Rampart Sample is Unable to pickup outgoing policy file

Posted by Manjula Peiris <ma...@wso2.com>.
The problem here is in security policy files we have assumed Axis2/C is
installed in ,
/home/AXIS2_USER/axis2/c/deploy. 

So when you are building the samples a script will replace the
AXIS2_USER  with the username(eg:- AXIS2_USER => dinesh). If we don't do
it then user have to manually edit four policy files. 

By the way this discussion should be moved to rampart-dev list.

Thanks

-Manjula.


On Sun, 2007-05-06 at 02:58 -0700, Dinesh Premalal (JIRA) wrote:
> Rampart Sample is Unable to pickup outgoing policy file
> -------------------------------------------------------
> 
>                  Key: AXIS2C-601
>                  URL: https://issues.apache.org/jira/browse/AXIS2C-601
>              Project: Axis2-C
>           Issue Type: Bug
>           Components: rampart
>     Affects Versions: 0.96, Current (Nightly)
>             Reporter: Dinesh Premalal
> 
> 
> After building rampart , I tried to run samples but they failed. Although my environmental variables of
> 
> AXIS2C_HOME=/home/dinesh/axis2c/deploy
> CLIENT_REPO=$AXIS2C_HOME/client_repo
> 
> log complains saying 
> 
> [rampart][rampart_Engine] Trying to build rampart context from file /home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml 
> [Sun May  6 15:28:53 2007] [info]  [rampart][rampart_Engine] Cannot get policy
> [Sun May  6 15:28:53 2007] [info]  [rampart][mod_rampart] mod_rampart shutdown
> 
> I have no idea where this path "home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml" came from ???
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Commented: (AXIS2C-601) Rampart Sample is Unable to pickup outgoing policy file

Posted by "Dinesh Premalal (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2C-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493920 ] 

Dinesh Premalal commented on AXIS2C-601:
----------------------------------------

I think these values came from client_repo/axis2.xml , because rampart_engine.c seems get that value from a parameter.  Moreover sec_echo/service.xml  sec_echo/outgoing_secpolicy.xml and sec_echo/incoming_secpolicy.xml , client_repo/outgoing_secpolicy.xml and client_repo/incoming_secpolicy.xml  files seems to hold some hard coded paths. I think we need to figure out better way of giving those files.

I think its better if we can calculate those paths with respect to $AXIS2C_HOME environmental variable. Or else we can ask from user to fill out those value before he run samples. You might have a better solution. Please correct me if I'm mistaken.

> Rampart Sample is Unable to pickup outgoing policy file
> -------------------------------------------------------
>
>                 Key: AXIS2C-601
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-601
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: rampart
>    Affects Versions: 0.96, Current (Nightly)
>            Reporter: Dinesh Premalal
>
> After building rampart , I tried to run samples but they failed. Although my environmental variables of
> AXIS2C_HOME=/home/dinesh/axis2c/deploy
> CLIENT_REPO=$AXIS2C_HOME/client_repo
> log complains saying 
> [rampart][rampart_Engine] Trying to build rampart context from file /home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml 
> [Sun May  6 15:28:53 2007] [info]  [rampart][rampart_Engine] Cannot get policy
> [Sun May  6 15:28:53 2007] [info]  [rampart][mod_rampart] mod_rampart shutdown
> I have no idea where this path "home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml" came from ???

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Assigned: (AXIS2C-601) Rampart Sample is Unable to pickup outgoing policy file

Posted by "Malinda Kaushalye Kapuruge (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Malinda Kaushalye Kapuruge reassigned AXIS2C-601:
-------------------------------------------------

    Assignee: Malinda Kaushalye Kapuruge

> Rampart Sample is Unable to pickup outgoing policy file
> -------------------------------------------------------
>
>                 Key: AXIS2C-601
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-601
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: rampart
>    Affects Versions: 0.96, Current (Nightly)
>            Reporter: Dinesh Premalal
>         Assigned To: Malinda Kaushalye Kapuruge
>
> After building rampart , I tried to run samples but they failed. Although my environmental variables of
> AXIS2C_HOME=/home/dinesh/axis2c/deploy
> CLIENT_REPO=$AXIS2C_HOME/client_repo
> log complains saying 
> [rampart][rampart_Engine] Trying to build rampart context from file /home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml 
> [Sun May  6 15:28:53 2007] [info]  [rampart][rampart_Engine] Cannot get policy
> [Sun May  6 15:28:53 2007] [info]  [rampart][mod_rampart] mod_rampart shutdown
> I have no idea where this path "home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml" came from ???

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Resolved: (AXIS2C-601) Rampart Sample is Unable to pickup outgoing policy file

Posted by "Malinda Kaushalye Kapuruge (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Malinda Kaushalye Kapuruge resolved AXIS2C-601.
-----------------------------------------------

       Resolution: Fixed
    Fix Version/s: Current (Nightly)

Fixed. 

> Rampart Sample is Unable to pickup outgoing policy file
> -------------------------------------------------------
>
>                 Key: AXIS2C-601
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-601
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: rampart
>    Affects Versions: 0.96, Current (Nightly)
>            Reporter: Dinesh Premalal
>         Assigned To: Malinda Kaushalye Kapuruge
>             Fix For: Current (Nightly)
>
>
> After building rampart , I tried to run samples but they failed. Although my environmental variables of
> AXIS2C_HOME=/home/dinesh/axis2c/deploy
> CLIENT_REPO=$AXIS2C_HOME/client_repo
> log complains saying 
> [rampart][rampart_Engine] Trying to build rampart context from file /home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml 
> [Sun May  6 15:28:53 2007] [info]  [rampart][rampart_Engine] Cannot get policy
> [Sun May  6 15:28:53 2007] [info]  [rampart][mod_rampart] mod_rampart shutdown
> I have no idea where this path "home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml" came from ???

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Commented: (AXIS2C-601) Rampart Sample is Unable to pickup outgoing policy file

Posted by "Malinda Kaushalye Kapuruge (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2C-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493968 ] 

Malinda Kaushalye Kapuruge commented on AXIS2C-601:
---------------------------------------------------

In rampart we have different modules and policy files to be loaded. These are NOT HARD CODED and MUST be specified in descriptor files. If you have specified correct paths this should work properly. Please check again whether you have defined them correctly.
Do not believe in scripts that deploys security policy files. Since it is only for demonstration purposes we have assumed that you have installed Axis2/C in your home directory, which was the best option, when we do not have a proper axutil library that can load modules given the relative paths. We made the life easy  by introducing scripts only for those who have installed axis2 in the home directory. :-) Note that in samples we have specifically asked you to check paths for modules and policy files, which you might have ignored.

> Rampart Sample is Unable to pickup outgoing policy file
> -------------------------------------------------------
>
>                 Key: AXIS2C-601
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-601
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: rampart
>    Affects Versions: 0.96, Current (Nightly)
>            Reporter: Dinesh Premalal
>
> After building rampart , I tried to run samples but they failed. Although my environmental variables of
> AXIS2C_HOME=/home/dinesh/axis2c/deploy
> CLIENT_REPO=$AXIS2C_HOME/client_repo
> log complains saying 
> [rampart][rampart_Engine] Trying to build rampart context from file /home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml 
> [Sun May  6 15:28:53 2007] [info]  [rampart][rampart_Engine] Cannot get policy
> [Sun May  6 15:28:53 2007] [info]  [rampart][mod_rampart] mod_rampart shutdown
> I have no idea where this path "home/dinesh/axis2/c/deploy/client_repo/outgoing-secpolicy.xml" came from ???

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org