1. Disable security constraints by commenting the tag in the WEB-INF\web.xml file where the WSA has been deployed in the Java Servlet Engine (JSE).
NOTE: There are multiple sections for security contraint in the web.xml and they will all need to be disabled.
<!–
<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>
–>
2. Check that the following entries are disabled in the ubroker.properties file:
adminAuth=0
webServerAuth=0
Or,
In the Progress/OE explorer, under security page of wsa1 properties, select «No user authentication» for «WSA Administration Authentication:» and uncheck the «Require WSA Administration Authorization» and save the change.
3. Restart the JSE in order for the changes to take effect.