Thanks Kumar for the feedback. I've gotten a chance to read your article. This is the bit that's going to give me trouble: [i]However for SAML based Mechanisms the Runtime would not know what is the incoming Caller Identity since the Principal and other Authorization Information would generally be inside the SAML Assertion sent by the Caller and only the WebService can decide what is the exact caller Identity.[/i]
I guess what I really want to do is make GlassFish my ServiceProvider, rather than the application. Are you saying in the above that I can't? My alternative would be to fit each running application with a filter that handles the SAML conversation (like
http://www.softwareborsen.dk/projekter/softwarecenter/brugerstyring/oio-saml-java) but I'd rather not go that way if I can.
I'm not using metro (I can if I should be), so I guess your article does not have a direct impact on my problem (or am I missing the point)?
Groeten,
Friso
[Message sent by forum member 'friso']
http://forums.java.net/jive/thread.jspa?messageID=394468