How To Use OWSM 11g Permission Base Authorization Policies For J2EE 1.5 Web Services
(Doc ID 1089613.1)
Last updated on AUGUST 02, 2023
Applies to:
Oracle Web Services Manager - Version 11.1.1.1 and later Information in this document applies to any platform.
Goal
NOTE: In the images and the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
This document explains how to apply OWSM permission base authorization policies for J2EE 1.5 JAX-WS web services. It will explain how different users can access or deny access to various web services.
The policies used in this example are.
oracle/wss_username_token_service_policy
oracle/binding_permission_authorization_policy
The web services will be created using JDeveloper 11g (11.1.1.2 in this example), then deployed to Oracle WebLogic 10.3 (10.3.2 in this example). Testing the web service will be conducted in Enterprise Manager for WebLogic Server, and also creating proxy clients in JDeveloper.
NOTE: In this article, all configuration details like server names, usernames, instance names, schema names, domain names, etc. used in the images and examples above represent a fictitious sample for clarity or are default installation values. These and any value placeholder values including the which may surround the placeholders should be replaced by the actual values used in your environment. Any similarity to actual environments, past or present, or users, living or dead, is purely coincidental and not intended in any manner.
Solution
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!