oracle/wss_http_token_client_policy
A credential
is uniquely identified by a map name and
a key name.
Typically,
the map name corresponds with the name of an application and all credentials
with the same map name define a logical group of credentials, such as the
credentials used by the application. All map names in a credential store must
be distinct.
Configure
Credential store in EM-Console
S1: Go to
weblogic Domain-> Security -> Credentials
S2: Click on
Create Map
S3: Enter
the map name as 'oracle.wsm.security' and click OK
S4: Select
the new Map and click on Create Key
è Select created Map
è Provide Key name:
è Type: Password
è User Name:
è Password:
è Confirm Password:
è Description:
You can
create multiple key in same map based on multiple secure service call.
Configure
SOA WS Policies in jdeveloper
S1. Right
click on Reference service open Configure
SOA WS Policies.
S2: In
Security click in + button you can view multiple Security policy.
S3: Select oracle/wss_http_token_client_policy
S4: Add
csf-Key and csf.map value which we configure on Credential store of EM console as mentioned above.
To
Attach/Detach policy on deployed composite
S1: go to deployed composite
S2: services and References
S3: Click on web service where you
want to attach policy
S4: Policy Configuration
S4: click on Attach/Detach
S5: select oracle/wss_http_token_client_policy -> attach
S6: attach on Directly Attached
Policies
S7: Validate -> OK
Note:
By default the value of
csf-key is set to basic.credentials, but you can create a new key in EM and use
that as an override.
Also, when not using the policy, adding the
properties oracle.webservices.auth.username and oracle.webservices.auth.password
with corresponding values will work for external references.
Same way we can implement Authentication for
client service in both SOAP and REST service.
No comments:
Post a Comment