security - Flex Blaze DS not passing OpenSSO authentication cookie? -
I have a set of custom web services These services have been protected by the OpenSSO on a Glassfish server when I open a browser I try to call up the Restime services directly, the OpenSSO prevents the request, then after requesting the user's credentials, the request for the reest service requests. The OpenSSO uses a session cookie on next requests (unless the session is invalid) I'm sure the piece is working properly.
We want to call these services from a Flex client to enable PUT and DELETE operations, we set up the blaze to proxy the lush requests for the REST service from the Flex client. When the security of rental services is disabled, this piece works great.
We are now trying to secure the entire application. We have kept Flex SWF in war and deployed glassfish. We have kept security around this resource and when a user tries to download SWF (via an HTML link in the war), then OpenSSO prevents the request, after which the application on successful authorization (such as the restime web For services).
The problem is - the cool calls made through the Flex application (via BlazeDS) are unsuccessful. The OpenSSO seems to hide these requests in the middle and then asking users for credentials. It does not seem that authentication cookies are being passed by Blazads Proxy (or perhaps).
How can I use the returned cookies from the original SSO authorization request and Blazads make them a restful web service?
Use firebug or any HTTP proxy to check for the following things -
< Ol>If the browser is sending a SSO cookie, then the SSO server can help you with additional details about yourself.
Comments
Post a Comment