Skip to main content

AliasSelector

2 replies [Last post]
vigdal
Offline
Joined: 2008-11-21
Points: 0

I am trying to set up my Metro to sign the request dependent on witch token the request is encrypted with. I have been able to achieve this with the use of AliasSelector.
To select the correct aliase I browse the RuntimeMap for the javax.security.auth.Subject property.
This works when I am using my JAX-WS generated client, but when I use another client based on OC4J client jar, this do not work. The RuntimeMap dos not contain the javax.security.auth.Subject property. Why is that ?

Thanks in advance.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Kumar Jayanti Guest
Offline
Joined: 2011-04-02
Points: 0

On Feb 19, 2013, at 3:31 PM, forums@java.net wrote:

> I am trying to set up my Metro to sign the request dependent on witch token
> the request is encrypted with. I have been able to achieve this with the use
> of AliasSelector. To select the correct aliase I browse the RuntimeMap for
> the javax.security.auth.Subject property. This works when I am using my
> JAX-WS generated client, but when I use another client based on OC4J client
> jar, this do not work. The RuntimeMap dos not contain the
> javax.security.auth.Subject property. Why is that ? Thanks in advance.
>
That is a Metro Specific Feature.

vigdal
Offline
Joined: 2008-11-21
Points: 0

OK, thanks. I suppose it all depends on the soap request. But what is the difference in my 2 attached requests that gives this feature?
Do you know an alternative approach to achieve this ?