tableau error ERROR com.tableausoftware.samlauthentication.handlers.SAMLAuthenticationFailureHandler - SAML Authentication Failed, please contact the administrator. org.springframework.security.authentication.AuthenticationServiceException: Incoming SAML message has no valid value for username attribute. Please verify ServiceProvider configuration in Identity Provider

when integrating Tableau with OAM 12c error is showing up in the tableau logs ERROR com.tableausoftware.samlauthentication.handlers.SAMLAuthenticationFailureHandler - SAML Authentication Failed, please contact the administrator. org.springframework.security.authentication.AuthenticationServiceException: Incoming SAML message has no valid value for username attribute. Please verify ServiceProvider configuration in Identity Provider Cause: Tableau require username attribute be passed on the SAML assertion. Tableau require following attribute username displayName email Solution: updated tableau SP profile "Attribute Name Mapping" value and add username as attribute and $user.attr.mail or $user.attr.username(check your OUD for the attribute name) as the value. if you are not passing displayName value. please add that into the Attribute Name Mapping table as well. Save the profile and test again

weblogic.management.DeploymentException: java.io.IOException: Error from fcntl() for file locking, Resource temporarily unavailable, errno=11

Weblogic error when starting the server weblogic.management.DeploymentException: java.io.IOException: Error from fcntl() for file locking, Resource temporarily unavailable, errno=11 techpaste.com/2012/07/java-io-ioexception-error-fcntl-file-locking-resource-temporarily-unavailable-errno11-weblogic/ in Adminserver.log

OHS 12c error oracle.security.fed.event.EventException: Could not find the AuthnRequest associated to the Assertion

Error: oracle.security.fed.event.EventException: Could not find the AuthnRequest associated to the Assertion CAUSE Configuration of OHS server for mod_weblogic for OAM. The "WLCookieName" parameter for the OHS server configuration is missing or has the wrong value. In this specifc case the value was incorrect, OAMSESSIONID, where as the OAM application uses "OAM_JSESSIONID". login_vh.conf:WLCookieName OAMJESSIONID should be: login_vh.conf:WLCookieName OAM_JSESSIONID. Solution: udpated the login_vh.conf file with the correct parameter and restart the OHS,It should fix the error

oam 12c IDP initiated URL

https://servername/oamfed/idp/initiatesso?providerid=https://applicationurl.com

oam 12c Download IDP metadata

1. login to oamconsole 2. Click on the Cinfuguration 3. go Down tp Settings section click on the View and select Federation. 4. Click Export SAML 2.0 Metadata

2nd OAM server in cluster unable to process the request OAM_JSESSIONID

SYMPTOMS Oracle Access Manager acting as the Service Provider (SP)WLS Managed Server Cluster with 2 OAM ServersOHS proxing mod_weblogic. There is no issue if only one WLS managed server is running When both WLS managed servers running OAM are started, the Federation flow fails. CAUSE Configuration of OHS server for mod_weblogic for OAM. The "WLCookieName" parameter for the OHS server configuration is missing or has the wrong value. In this specifc case the value was incorrect, OAMSESSIONID, where as the OAM application uses "OAM_JSESSIONID". The above fix the issue that two wls_oam1/wls_oam2 could not be started for federation to work.

JDK updated error jdk-8u341-linux-x64 :Caused by: java.net.URISyntaxException: Malformed IPv6 address at index 8

After updating JDK to new version jdk-8u341-linux-x64, IDM components are not coming up. It is a bug. here is how i fixed it error error:Caused by: java.net.URISyntaxException: Malformed IPv6 address at index 8 I have eadded below value to setDomainEnv.sh JAVA_PROPERTIES="-Dcom.sun.jndi.ldapURLParsing=legacy Also i have added above attribute to each Manager server Start stop section in Arguments section -Dcom.sun.jndi.ldapURLParsing=legacy