Deploy a New Web Service Error

[kirsch59]

OS: Window Server 2003
Progress Version 10.1C
IIS 6.0

I'm trying to create a web service using Proxygen/Web Service Adapter/AppServer etc. In Progress Explorer I'm accessing the Web Services Adapter/wsa1 and selecting Deploy A New Web Service. I select the .wsm file and hit OK. The deployment information that I setup in ProxyGen is displayed. It looks good and when I click OK I get the following error:

Web Server Authentication failed.
Please re-enter Web Server login information and re-do your last action.

I get prompted for the login information and then enter it in. I do the process over, Deploy A New Web Service... and I get the same error message. I keep looping.

When I check the status of wsa1. It looks good. Stuff is running and enabled.
Webspeed brokers/agents are working.

How do I get pass this problem?

Thanks
Mark

 

[RealHeavyDude]

You need to check the properties of your WSA instance - there are security settings which determine how security must be handled and thus whether you are forced to authenticate when accessing it.

You can find these settings in the ubroker.properties file in the section for your WSA instance, or, much easier, when you use the Progress Explorer.

Out of experience I would recommend you to switch off security until the thing is running and then tighten security step by step.


Heavy Regards, RealHeavyDude.

 

[MaximMonin]

You can change security rules in tomcat configuration.
check tomcat/webapps/wsa1/WEB-INF/web.xml file

and comment lines with security constrain

<!--

<security-constraint>
<web-resource-collection>
<web-resource-name>wsa1 Admin</web-resource-name>
<url-pattern>/wsa1/admin/*</url-pattern>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>PSCAdmin</role-name>
<role-name>PSCOper</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
-->

<!--
<security-constraint>
<web-resource-collection>
<web-resource-name>wsa1 Web Services</web-resource-name>
<url-pattern>/wsa1/</url-pattern>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>enter_jse_role_name</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
-->

<!--
<security-constraint>
<web-resource-collection>
<web-resource-name>wsa1 WSDL Access</web-resource-name>
<url-pattern>/wsa1/wsdl/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>enter_jse_role_name</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
-->

 

[kirsch59]

The problem was a security settings. The WSA had Require WSA Administration Authorization checked; thus, a login for PSCAdmin and PSCOper was required by the ServletExec adapter. I unchecked Require WSA Administration Authorization option using the Progress Explorer and reloaded ServletExec; however, PSCAdmin and PSCOper was still being authorized.

As a result, I edited ServletExec's web.xml for WSA. I removed
<auth-constraint>
<role-name>PSCAdmin</role-name>
<role-name>PSCOper</role-name>
</auth-constraint>

reloaded it and then was able to deploy the Web Service.