Ace

 These tips will help you get that extra data to help with self-troubleshooting: WebLogic Installer in debug mode: There are times when a webLogic installer fails in the middle and you do not have a clue what is going wrong (except for a single fat error message). Consider starting the installer with extra bit of logging enabled. Here is the syntax and applicable logging level flags (holds true for 11g as well):       <installer_name> [-mode={console|gui|silent}] [-silent_xml=<file_name>] [-log=<file_name>] [-log_priority={debug|info|warn|error|fatal}]        e.g., wls1032.exe -mode=console -log install.log -log_priority=debug Applying patch with debug logging level: Enable debug logging when applying the patch to get more insight into what is happening:        bsu.sh [-log=<file_name>] [-log_priority={trace|debug|info|warn|error|fatal}] Checking the Debu...

In an IdP-initiated use case, the identity provider is configured with specialized links that refer to the desired service providers. These links actually refer to the local IdP's Single Sign-On Service and pass parameters to the service identifying the remote SP. So instead of visiting the SP directly, the user accesses the IdP site and clicks on one of the links to gain access to the remote SP. This triggers the creation of a SAML assertion that will be transported to the service provider. Here, I discuss the scenario when: WebLogic is IdP WebLogic is SP Suppose we have two domains (SrcDom1 and DstDom1) such that: SrcDom1 - (IdP) - host:27001 - metadata file is idp.xml DstDom1 - (SP) - host:37001 - metadata file is sp.xml - service application deployed as "appB.war" with one of the protected urls as: http://host:37001/appB/admin/services.jsp - Default URL (defined from admin console at "SERVER_NAME/Configuration/Federation Services/SAML 2.0 Serv...