To reset the Multi-Factor Authentication (MFA) for your admin account in Oracle Cloud Infrastructure (OCI), follow these steps.


1. Access Oracle Cloud Console:

  • Log in to the OCI Console with your admin credentials.

2. Navigate to Identity & Security:

  • From the main OCI dashboard, go to the “Identity & Security” section.
  • Under Identity, select “Users”.

3. Find Your Admin User:

  • Search for your admin user account in the Users list.

4. Reset MFA:

  • Once you’ve located the admin account, click on the username to open the user details.
  • On the user’s details page, scroll down to the “Multi-Factor Authentication” section.
  • There will be an option to “Reset MFA” or “Remove Device”.
  • Click “Reset MFA” to remove any previously configured MFA devices.

5. Reconfigure MFA:

  • After resetting, you will need to reconfigure MFA when you log in again. OCI will prompt you to set up a new MFA device.

6. Follow the Instructions for Re-Enrollment:

  • You will be asked to scan a new QR code using an authenticator app (like Google Authenticator or Authy) and provide a verification code to finalize the setup.

Once completed, MFA will be reset, and you can log in using your new MFA device.

Comments

Post a Comment

Popular posts from this blog

ORA-05031 error in Oracle Autonomous Database

  The ORA-05031 error in Oracle Autonomous Database indicates that the SGA (System Global Area) usage for a Pluggable Database (PDB) has exceeded its limit. This issue can arise due to resource constraints or misconfiguration and can significantly impact the performance of your database, especially during resource-intensive operations like Oracle Data Pump. Here are some steps to address and prevent this issue: mmediate Actions Check Resource Usage: Use the following query to monitor the SGA usage: SELECT NAME, VALUE / 1024 / 1024 AS VALUE_MB FROM V$SYSSTAT WHERE NAME IN ( 'session pga memory' , 'session pga memory max' , 'session uga memory' , 'session uga memory max' ); Verify if the SGA_TARGET or MEMORY_TARGET settings are close to the configured limits. Terminate Long-Running Sessions: Identify and terminate any runaway sessions or jobs that are consuming excessive resources: SELECT SID, SERIAL#, PROGRAM, STATUS, SQL_ID FROM V$SESSION W...
Read more

What's New with Oracle Cloud Guard in OCI?

 Oracle Cloud Guard is a game-changer for securing your cloud environment. Here are the top 10 features to know: Automated Threat Detection : Cloud Guard continuously scans for potential security risks across your OCI resources, providing automated detection and alerting. Built-in Remediation : With preconfigured policies, Cloud Guard offers automated remediation actions to address security threats instantly. Comprehensive Visibility : Gain end-to-end visibility into your OCI environment with dashboards and reports, helping you monitor and track risks in real-time. Customizable Policies : Cloud Guard allows you to tailor security policies based on your organization’s unique compliance needs. Risk Scoring : Each resource is assigned a risk score, enabling you to prioritize the most critical threats for immediate action. Incident Response Automation : Automate responses to incidents using predefined rules, reducing manual intervention and response time. Integrations with Oracle Secur...
Read more

Upgrade Pluggable Database to Oracle Database 23ai

  Here’s a simplified way to upgrade your Oracle Database in OCI to Oracle Database 23c AI using a refreshable clone PDB and AutoUpgrade. Benefits of This Approach: Reduced Downtime: It minimizes downtime compared to an in-place upgrade. New Base Database System: You’ll get a new system with an updated OS and Oracle Grid Infrastructure version. You can use this approach for a Base Database Service, Exadata Database Service, Exadata Cloud@Customer, or any Oracle Database option. My Environment PDB to Upgrade: SALES Source: Version: 19.23.0 Name: DBS19 Target: Version: 23.4.0 Name: DBS23 Steps to Upgrade: 1. Prepare AutoUpgrade Download the latest version of AutoUpgrade from My Oracle Support. Copy it to both source and target systems, optionally placing it in $ORACLE_HOME/rdbms/admin . Create an AutoUpgrade config file ( sales.cfg ), and save it on both servers: global.autoupg_log_dir=/u01/app/oracle/cfgtoollogs/autoupgrade global.keystore=/u01/app/oracle/cfgtoollogs/keystore...
Read more