Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Secure web services > Secure bus-enabled web services


Ovveride the default security configuration between bus-enabled web services and a secure bus

To override the default configuration through which the bus-enabled web services component accesses a secure service integration bus, you configure an authentication alias that the service integration resource adapter uses to access the bus.

To use bus-enabled web services when bus security is enabled, your web services clients must provide suitable credentials when making requests. Your clients can provide credentials either by using WS-Security or by using HTTP basic authentication, as described in Authenticate web services clients using HTTP basic authentication. For HTTP basic authentication, application security must also be enabled and, depending on which of these authentication schemes you use, the endpoint listener application must be appropriately configured as described in Password-protecting inbound services. When you use HTTP basic authentication, you map the AuthenticatedUsers role to the special "AllAuthenticatedUsers" group (or to some other suitable authenticated group or user); when you use WS-Security you do not need to map the endpoint listener AuthenticatedUsers role unless Application Security is enabled, in which case you map the AuthenticatedUsers role to the special "Everyone" group. See Assign users and groups to roles.

The default configuration that the bus-enabled web services component uses to access a secure bus is as follows:

See Bus-enabled web services default configuration for accessing a secure bus.

We can override this default configuration by defining an authentication alias that the service integration resource adapter uses to access the bus. Using an authentication alias does not make the configuration more secure. However, you might want to use an alias for consistency of approach if we have other application servers running under WAS v6.0.x, or to support your internal business controls for use of IDs and passwords.


Procedure

  1. In the navigation pane, click Service integration -> Buses -> security_value -> [Related Items] JAAS - J2C authentication data .
  2. Create a J2C authentication alias.

  3. Configure authentication for the resource adapter...

    1. In the admin console navigation pane, click Resources -> Resource Adapters -> J2C activation specifications -> activation_specification_name , where activation_specification_name is SIBWS_OUTBOUND_MDB.

    2. In the Authentication alias drop-down list, select the authentication alias that you created.

    3. Click Apply.
    Optional. Disable the default authentication configuration.

    If you configure an authentication alias you need not also disable the default configuration. If an authentication alias exists, it overrides the default configuration. This means that if you use an authentication alias that is authorized to access the bus then the communication will succeed, and if you use an authentication alias that is not authorized to access the bus then the communication will fail, irrespective of the default settings. However if you subsequently remove the authentication alias from the activation specification, the default configuration will again take control and (if not disabled) will allow the service integration resource adapter to continue to access the bus. See Bus-enabled web services default configuration for accessing a secure bus.

    To disable the default authentication configuration...

    1. In the admin console navigation pane, click Resources -> Resource Adapters -> J2C activation specifications -> activation_specification_name -> [Additional Properties] J2C activation specification custom properties , where activation_specification_name is SIBWS_OUTBOUND_MDB.

    2. In the list of custom properties, click useServerSubject
    3. Change the Value for the useServerSubject property from "true" to "false".

    4. Click OK.

  4. Save your changes to the master configuration.
  5. Close the admin console.

+

Search Tips   |   Advanced Search