Jira Data Center error "We cant log you in right now" message while trying to login to confluence using SSO

Error, "We cant log you in right now" message while trying to login to Jira using SSO Issue: Once you are authenticated from the Okta or any IDP, IDP will send the user to Jira or any SP, looks like the SP is not accessable by IDP to send the users to. Check your nextworking configuration to see if communication is working between these applications.

Okta CrowdStrike intergration and Zero Trust Assisment(ZTA) trobleshooting

Okta side 1. Enable integration between CRW and Okta 2. configure End Point Security 3. implement Authenticaiton Policy with overallscore logic 4. Enable/Configure FastPass -- user have to use FastPass when loggin in otherwise ZTA will not enforce. 5. Install Okta Client agent on the target system. CrowndStrike Side 1. Make sure to have 2 integration are done 1. Okta to CrowndStrike using SAML or OIDC 2. enable ZTA in Okta 2. Install/Configure CrowdStrike agent. Application Side( you are trying to implement ZTA) 1. Install/Configure OktaVerify/FastPass on the computer you are trying to login.

Okta AWS IAM Identity Center Integration error "Something went wrong Looks like this code isn't right. Please try again."

Error Something went wrong Looks like this code isn't right. Please try again. Senario, You integrated okta with AWS Identity Store following the Okta instructions but when you test, you are getting error. Reason, Okta is sending attribute value that does not exists in AWS Identity Store. Value in Okta or AWS Identity store does not match. Solution: IAM Identity Center is like a directory. when you are logging into the AWS you are beig authenticated by different store. You need to make sure user who are going to login to IAM Identity Center has users information there. either change the username value after clicking on Provisioning Tab of IAM Identity Center in Okta and change the username value or match the default username value to "IAM Identity Center" user information.

JIRA SSO with OAM 12c issue

After integrating Jira with OAM 12c, after authentication from OAM, user is landing on the OAM error page. It is not issue of integration. in the error logs message is about the Relay State that is miss leading. Here is what i did to fix it. Solution: Change the Federation configuration on the Jira(SP). change "Identity Provider Single Sign on URL" to send the SAML Request to OAM at https://your server name .com/oamfed/idp/samlv20. instead of at https://your servername.com/oam/server/fed/sp/sso making this change will fix integration issue. Jira will get the response from the new url and it will forward the user to the jira page.

OAM 12c Jan 2023 bundle patch error [FAILED] Environment has not met the minimum DBClient version(Database_Client 12.2.1.19.0) requirement.

error when running pre-stop oid command [FAILED] Environment has not met the minimum DBClient version(Database_Client 12.2.1.19.0) requirement. Solution: Run the following command to fix the issue. to do so you have to shutdown the OID run the below commmand and start the OID ../../../IDM_SPB_12.2.1.4.230117/tools/spbat/generic/SPBAT/logs/bas01occsiidm02_oid_12.2.1.4.230117/preCheck/dbclient/dbclient_upgrade.sh

to kill all the nodemanager

kill -9 `ps -ef | grep [N]odeManager | awk '{print $2}'`

Error Trigger Listener QuartzTriggerListener.triggerMisfired

error Solution in order to fix this issue increase the dataBasePoolSize this configuration is in the oim-config.xml export the MDS schema and update this value and improt again.

to check Alias command in linux

keytool -list -keystore /../../../jdk/jdk1.8.0_341/jre/lib/security/cacerts -storepass changeit | grep Alias

OAM 12c error Caused By: oracle.security.fed.controller.frontend.action.RequestHandlerRuntimeException: An error occurred while verifying/signing/encrypting/decrypting a message java.security.NoSuchAlgorithmException: http://www.w3.org/2001/04/xmldsig-more#rsa-sha256 Signature not available; oracle.security.fed.security.util.CryptoException: java.security.NoSuchAlgorithmException: http://www.w3.org/2001/04/xmldsig-more#rsa-sha256 Signature not available

error Caused By: oracle.security.fed.controller.frontend.action.RequestHandlerRuntimeException: An error occurred while verifying/signing/encrypting/decrypting a message java.security.NoSuchAlgorithmException: http://www.w3.org/2001/04/xmldsig-more#rsa-sha256 Signature not available; oracle.security.fed.security.util.CryptoException: java.security.NoSuchAlgorithmException: http://www.w3.org/2001/04/xmldsig-more#rsa-sha256 Signature not available Reason This error happen once we applied the OCT 2022 patch and changed the algorithm to sha256 from sha1 it is a bug and oracle provided the patch Oracle Access Manager (OAM) Federation Login Flow Fails "Incorrect username or password was specified" After Applying OAM BUNDLE PATCH 12.2.1.4.220906 (Doc ID 2905580.1) Solution Apply the above bundle patch to fix the issue

once certificate is updated follow the below steps to update database

once certificate is updated dow the following downloadAccessAtrificats(domainHome="/../../domains/IAMAccessDomain",prosFile="/../dbschema.properties") upload all certs into .oamkeystore and amtruststore saveAccessAtrificats(domainHome="/config/oam_domain",profFile="/config/oam/oam_domain/bin/dbschema.properties") if you dont run save command, new information will not show up

OAM 12c SAML Response needs value in firstname.lastname format in the response

Requirenment. We need to achieve a reuirenment where SAML response should be firstname.lastname but our username attribute from the OUD have email address. Tableau require username attribute in this formate. Solution. In a SAML response we have to contatinate the firstname and lastname values to achieve username attribute value here is the expresion we used in the SAML response username value. ${user.attr.givenname}.${user.attr.sn} results was firstname.lastname

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

Insufficient free space in /tmp/orcl8124660.tmp to extract the installer

java error when installing any oracle OIG solution. when running below command $java -d64 -jar fmw_12.2.1.4.0_infrastructure.jar Error: com.oracle.cie.nextgen.launcher.LogUtils - Extracting to /tmp/orcl8128795323290514660.tmp. SEVERE [1] com.oracle.cie.nextgen.launcher.Launcher - Insufficient free space in /tmp/orcl290514660.tmp to extract the installer. Actual 107 MB. Required 1574 MB. SEVERE [1] com.oracle.cie.nextgen.launcher.Launcher - Insufficient free space in /tmp/orcl8514660.tmp to extract the installer. Solution: you dont have enought space on /tmp or tmp dont allow to execute any command at that location for security reason. the solution is provide different tmp location use below command to setup different location(make sure to have these directories) export _JAVA_OPTIONS="-Djava.io.tmpdir=/u01/orcle/tmp"

how to change group gid in a linux

1. login to user account and run id command you will get users current uid, gid information of the account, suppose oracle gid was 1004 and you want to change it to 1040 2. login to root and run the following command to change the gid groupmod -g 1040 oracle 3. now login to the user account and run the id command again. you will see new gid of the user group