When you install the WSA component of the WSTK, you can choose to enable security. In this case, WSA security is preset so that users who try to access WSDL are not authenticated. This authentication can be enabled.
To enable authentication for WSDL:
1. Choose an authorization role name to identify users who get access to all of a WSA instance's WSDL.
2. Using a text editor, edit the WSA instance's web.xml file as follows:
a. Uncomment or add a <security-constraint> element for the URL path for WSDL. The <security-constraint> element might appear as follows:
b. Add a <role-name> element to the <security-constraint> element to hold the authorization role name you chose. A <role-name> element has the following syntax:
3. Modify the Java container to add your user's accounts and grant them membership to the chosen role.
4. Modify the WSA instance's properties to enable authorization for WSDL. Use one of the following techniques:
If the WSA instance is local (the WSA resides on the AdminServer machine), select the WSA instance in OpenEdge Management or OpenEdge Explorer, click Configuration, and choose Properties. Select Security to display the Security tab. In the Security tab, enable authentication for WSDL.
If the WSA instance is remote (the WSA instance does not reside on the AdminServer machine), using a text editor, in the ubroker.properties file from which the WSA instance is initialized, in the properties for the WSA instance, set wsdlAuth to 1 (one). The possible values for wsdlAuth are listed in the following table.