Total Pageviews
Wednesday, December 28, 2022
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
Thursday, December 22, 2022
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
Thursday, December 8, 2022
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
Subscribe to:
Posts (Atom)