Compared to what Glass Fish knows about Web Logic, this is still a very limited set of parameters. And we are still looking forward to even less xml configuration with further Java EE versions. What Glass Fish knows about Web Logic Glass Fish Server offers limited support for the weblogic-application.xml, weblogic.xml, and deployment descriptor files.The only element in that Glass Fish Server supports is security.The sample application (Federation Sample App) deployment descriptor is configured to allow access to resources under /protected/* to users that belong to "Federation Sample App Members" group.
The goal behind that obviously is to allow a Glass Fish application to be deployed more easily to Web Logic Server and vice verse.In the Advanced Settings panel, enter the following: Single Logout URL is the logout URL of the sample application.HOST: PORT is the host and port of the managed server running the sample application. Open the application page, go to “SSO Configuration” tab and click “Download IDCS Metadata” and save the XML file (IDCSMetadata.xml).In the Attribute Configuration section, add one Group Attribute, with the following information: Name must be "Groups" and format must be "Basic" so the SAML Identity Asserter can pick up the groups attributes when the SAML Assertion is posted back to WLS. Users need to be assigned to applications in the Id P (IDCS) before they can authenticate to those apps. Select the users that should have access to the application.We do it by assigning individual users to the application in the "Users" tab. Upload the "IDCSMetadata.xml" file to the Authentication and click on the SAML2Identity Asserter.Go to the Management tab and click "New", and select "New Web Single Sign-On Identity Provider Partner".Enter the following information for the Id P Partner: Name: IDCS-Id P Choose the and click "OK" button.Click on the "IDCS-Id P" partner from the Identity Provider Partners list.Fill in the following information: the "Redirect URIs" are all the URIs that should be protected by the SAML SSO policy, that is, every URI that would trigger the SAML SSO flow and/or require authorization. this is the key point of this use case, by enabling "Virtual User" and "Process Attributes" we will allow users that are only defined in the Id P (IDCS) to login to our application.One of the main goals of Oracle's strategy for Glass Fish server was to "integrate with Fusion Middleware and Products" (source: Community Roadmap May, 2010).Back in this year you heard a lot of fears and rumors about the two servers becoming one.