cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prachi Damle (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
Date Thu, 20 Jun 2013 20:58:22 GMT


Prachi Damle commented on CLOUDSTACK-2927:

I think I found out why the EC2AuthenticationHandler is not getting invoked.

Compared to a 3.0.x setup, I see that the axis2.xml file is different for apache master setup.
In 3.0.x this file contains the hookup needed to tell axis2 to invoke the AuthenticationHandler
for ec2.
I have attached the axis2.xml file I see in a 3.0.x setup and it contains following:

       <phase name="ec2authentication">
             <handler name="InFlowEC2Auth"
                    <order phase="ec2authentication"/>

     <phase name="s3authentication">
       <handler name="InFlowS3Auth"
                <order phase="s3authentication"/>

You can check if the section above is present in your master setup - file is under cloudstack-bridge/webapps/awsapi/WEB-INF/conf
If it is missing , can you add this section to your file - or just use the 3.0.x file in your
setup and restart and try the SOAP call?

I actually see that in our source, the file here is correct:  awsapi/resource/Axis2/axis2.xml
- so if this works, it may be that packaging needs to use this version.

> [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
> -------------------------------------------------------------------
>                 Key: CLOUDSTACK-2927
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: AWSAPI
>    Affects Versions: 4.2.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>             Fix For: 4.2.0
>         Attachments: awsapi.log
> Set enable.ec2.api to true.
> Register user using cloudstack-aws-api-register.
> Make any SOAP API call e.g. ec2-describe-images using ec2 tools.
> Output - Server.InternalError: An unexpected error occurred
> Attached awsapi.log for log details

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message