Other Okta products and features that leverage the impacted streaming service, such as User Search for entity updates and ThreatInsights for event analysis, remained available throughout the impact window and operated with partially stale data until processing delays were resolved. Learn how to troubleshoot Okta Verify problems. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zHkXUAU"},"Id":"a1P1Y000007zHkXUAU","CreatedDate":"2019-10-01T05:06:40.000+0000","IncidentId__c":"a9C1Y0000004DyLUAU","UpdateLog__c":"Workaround has been deployed to Cell OK1. https://platform.cloud.coveo.com/rest/search, https://support.okta.com/help/s/global-search/%40uri, https://support.okta.com/help/services/apexrest/PublicSearchToken?site=help, TOTP (on by default) (Android and iOS only), Response example (waiting for 3-number verification challenge response), Sign in with an Okta Verify push notification (iOS), Sign in with an Okta Verify push notification (Android), Enroll Okta Verify in an authentication enrollment policy, Users verify their identity by entering a six-digit code generated by. Our monitoring is showing recovery and the next update will be in 12 hours or sooner if additional information becomes available. email developers@okta.com with your org. The service interruption was fully restored at 9:50AM PST.\r\n\r\nAdditional root cause information will be available within 2 Business days. Between 11:47am (PT) and 12:18pm (PT) a small subset of flow executions were terminated since they exceeded the maximum redelivery attempts. We will provide an update within the next 30 minutes. Impacted customers were instructed to upgrade to Okta Verify 7.9.2.\r\n\r\n \r\n\r\nPreventative Actions:\r\n\r\nOkta is updating our app rollout monitoring strategy to detect issues earlier in the release cycle. Okta continued monitoring and confirmed at 1:18PM, that the service was restored and operating as expected. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mSEDEA2"},"Id":"a1P4z000009mSEDEA2","CreatedDate":"2023-02-13T19:51:25.000+0000","IncidentId__c":"a9C4z000000YzlJEAS","UpdateLog__c":"We appreciate the collaboration and partnership of the Okta customers and community that works with Okta to identify and resolve issues in the preproduction [Preview] (https://www.okta.com/resources/datasheet-oktas-preview-sandbox/) sandbox environment before these issues reach production. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000BAKjKEAX"},"Id":"a1P4z00000BAKjKEAX","CreatedDate":"2021-09-03T03:23:48.000+0000","IncidentId__c":"a9C4z000000wk3CEAQ","UpdateLog__c":"We sincerely apologize for any impact this incident has caused to you and your business and your customers. \r\n\r\n \r\n\r\nRoot Cause:\r\n\r\nAfter investigation and collaboration with Okta customers, it became evident that the issue matched a broader impact of Windows machines and server connection attempts being blocked by third party firewall devices and services. Is there liablility if Alice startles Bob and Bob damages something? Find centralized, trusted content and collaborate around the technologies you use most. After deploying the fix, we are still seeing a number of issues. Further updates can be found in the admin portal under EX147785 and MO147789.\"\r\n\r\nOkta will post additional information as we learn it from Microsoft. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mSKfEAM"},"Id":"a1P4z000009mSKfEAM","CreatedDate":"2023-03-04T02:12:49.000+0000","IncidentId__c":"a9C4z000000YznUEAS","UpdateLog__c":"Okta has completed all automated remediation actions. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P2A00000G0UpsUAF"},"Id":"a1P2A00000G0UpsUAF","CreatedDate":"2018-03-07T21:25:07.000+0000","IncidentId__c":"a9C2A000000PBikUAG","UpdateLog__c":"The issue impacting API Access Management in US Preview cell has been resolved for the majority of customers. Customers using custom domains were able to successfully authenticate, SSO, and access end user resources, however administrative tasks would have been impacted. The user selects the number in Okta Verify on their mobile device that matches what they see in the sign-in instructions. At 6:30 AM PST, our monitoring shows improvements in network connectivity. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRUyEAM"},"Id":"a1P4z000009mRUyEAM","CreatedDate":"2022-10-17T14:47:47.000+0000","IncidentId__c":"a9C4z000000Yzh7EAC","UpdateLog__c":"An issue impacting Okta Verify Application version 7.9.1 for Android devices for all end users in all cells has been identified and is being investigated. At approximately 2:17 AM PST, Okta succeeded in initiating a forced fail-over within US Cell 4 to regain cluster stability and restore service. I created a simple use-case in nodejs, but I get permission error and I didn't find any solution to resolve this issue. Site design / logo 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRj0EAE"},"Id":"a1P4z000009mRj0EAE","CreatedDate":"2022-11-17T00:48:14.000+0000","IncidentId__c":"a9C4z000000YzhvEAC","UpdateLog__c":"Following is the RCA summary for a recent incident where a third party provider or downstream service experienced an issue which impacted the Okta service. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000B1xW7EAJ"},"Id":"a1P4z00000B1xW7EAJ","CreatedDate":"2021-06-15T21:42:06.000+0000","IncidentId__c":"a9C4z000000oLmzEAE","UpdateLog__c":"Root Cause Analysis:\r\n\r\nProduct: Okta Workflows\r\n\r\nOn June 11, 2021 at approximately 10:14AM PDT, Okta detected a higher volume of Workflows execution requests on US Cells 1, 2, 3, 4, 6, 7 and 11 impacting the workflows service. We are actively investigating and will update this message with more information as soon as we have it. ","CurrencyIsoCode":"USD"}]. Additional root cause information will be provided here shortly. Okta isolated the root cause of the issue and restarted service components to restore network connectivity. Users that develop, host, or debug websites locally often enable this option. The change that caused the incident will be rolled out again only after additional validation and safeguards are put in place. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mSKkEAM"},"Id":"a1P4z000009mSKkEAM","CreatedDate":"2023-03-04T03:39:35.000+0000","IncidentId__c":"a9C4z000000YznUEAS","UpdateLog__c":"Okta is developing a KB article and additional information to assist customers that were impacted by this issue. \r\n\r\n\r\nRoot Cause Summary: \r\n\r\nDuring a maintenance task to align network rules across infrastructure, a set of rules was inadvertently changed from count mode to block mode. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000007eJbWUAU"},"Id":"a1P0Z000007eJbWUAU","CreatedDate":"2018-04-25T02:43:56.000+0000","IncidentId__c":"a9C0Z000000TNeqUAG","UpdateLog__c":"Root Cause Analysis:\r\n\r\nOn April 24th, at 7:53am PDT, Okta experienced a broad service disruption to US Cell 2. T-Mobile, Sprint, and MetroPCS customers are experiencing the majority of delays currently. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000009QR1yUAG"},"Id":"a1P1Y000009QR1yUAG","CreatedDate":"2020-08-26T23:11:29.000+0000","IncidentId__c":"a9C1Y0000008PZGUA2","UpdateLog__c":"We have customer confirmation of the fix on US Cell 7, and continue deploying it to the remaining cells. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mS77EAE"},"Id":"a1P4z000009mS77EAE","CreatedDate":"2023-01-26T18:40:51.000+0000","IncidentId__c":"a9C4z000000YzkkEAC","UpdateLog__c":"We apologize for any impact this incident may have caused to you and your business. At 2:20pm PDT Okta suspended the rollout of Okta Verify 5.0.2 for iOS and continued to investigate the problem.
Troubleshoot Okta Verify on Windows devices | Okta Users are prompted to set up biometrics when they create an Okta Verify account or the next time they attempt to sign in with Okta Verify on the enrolled device. Your Okta Verify account might still be tied to your original app installation. We are actively working to mitigate job processing delays and will continue to provide updates as they are available. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mS6nEAE"},"Id":"a1P4z000009mS6nEAE","CreatedDate":"2023-01-26T02:19:15.000+0000","IncidentId__c":"a9C4z000000YzkfEAC","UpdateLog__c":"We sincerely apologize for any impact this incident has caused to you, your business, and your customers. Okta admins should discourage users for whom push notifications are currently working, from upgrading to version 5.0.5, as this may cause their push notifications to break.\r\n\r\nOkta is actively working on an additional fix that will fully resolve the issue for all upgrade paths. ","Status__c":"Resolved","Start_Date__c":"2022-12-21","End_Date__c":"2022-12-21","Last_Updated__c":"2022-12-23T18:57:27.000+0000","LastModifiedDate":"2022-12-23T18:57:27.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Size__c":"Medium","Incident_Title__c":"Advanced Server Access (ASA) is currently experiencing an issue with the service","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:5;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:10;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Advanced Server Access","Start_Time__c":"2022-12-21T20:15:00.000+0000","CreatedDate":"2022-12-21T20:19:20.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v57.0/sobjects/Incident__c/a9C4z000000YziUEAS"},"Id":"a9C4z000000YziUEAS","Duration__c":79,"Log__c":"Please note that Okta monitoring detected an outage with Oktas internal Salesforce Service Cloud application at 11:02 AM PST. Service has returned to normal as of 11:30 AM PST. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zKsoUAE"},"Id":"a1P1Y000007zKsoUAE","CreatedDate":"2020-04-16T00:41:22.000+0000","IncidentId__c":"a9C1Y0000004EI1UAM","UpdateLog__c":"Okta has observed an issue with the new 5.0.2 version of Okta Verify for iOS. Other requests, and End-Users and Administrators who already had an active session did not experience any impact.\r\n
\r\nThe issue surfaced when the cell's session token management cluster became overwhelmed by a sudden increase in the number of active sessions. At the same time, Okta began receiving reports from customers who were experiencing timeout errors and they were impacted in the following ways:\r\n\r\n- Workflow API calls did not complete execution and timed out\r\n\r\n- Workflows Console Folder view errors/timeouts were experienced until 11:35AM\r\n\r\n- Workflows Designer Test flow timeout errors were experienced until 12:16PM\r\n \r\nUpon investigation, Okta identified a workflow that was generating a large incoming workload and took immediate action to isolate it. The corresponding reduction in workflow process completion triggered internal monitoring and alerting systems and triggered immediate intervention by Okta. When opening the Okta Mobile for Android application, end users may be logged out of their account and encounter the following message: Detected possible malicious activity when establishing a secure connection to Okta. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P2A00000Fjr2PUAR"},"Id":"a1P2A00000Fjr2PUAR","CreatedDate":"2018-03-30T15:15:50.000+0000","IncidentId__c":"a9C2A000000bmK1UAI","UpdateLog__c":"We are currently working with Microsoft who has acknowledged the issue via incident MO133118. At approximately 2:30pm PDT, Okta started to see improvements in Single Sign-On (SSO) and the Provisioning services. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRb6EAE"},"Id":"a1P4z000009mRb6EAE","CreatedDate":"2022-11-01T19:58:44.000+0000","IncidentId__c":"a9C4z000000YzhREAS","UpdateLog__c":"An issue impacting Multifactor Authentication for end users in all cells has been identified and is being investigated. We are committed to implementing improvements to the service to prevent future occurrences of this incident.\r\n\r\n\r\nDetection and Impact\r\n\r\nOn March 29th at 10:39AM(PT) Oktas monitoring notified our team of elevated errors and that users were unable to access the Okta service in US Cells 5 and 10. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRlQEAU"},"Id":"a1P4z000009mRlQEAU","CreatedDate":"2022-11-25T18:45:18.000+0000","IncidentId__c":"a9C4z000000YziPEAS","UpdateLog__c":"Okta continues to monitor the current issue with our partners regarding the SMS delivery delays using US-based phone numbers. Regardless of which verification options you select, end users are still enrolled automatically in all of them. This issue has been resolved. The missing tables have been restored. \r\n\r\n\r\nDetection and Impact: \r\n\r\nOn February 1st, 2023 at 8:10pm (PT), Okta deployed updates to US Preview Cell OP1. After further investigation we have identified a workaround to help to address the issue. As of 11:45 am PDT, OKTA services were fully restored. At this time user provisioning has been disabled, we are working to restore this functionality and investigating the root cause. \r\n\r\nOkta strongly recommends that customers always configure multiple MFA factors, so that in cases such as this, where the telecommunications infrastructure is impacted, end users are able to authenticate leveraging another factor. Ensure that your network connection is stable. The date and time on your device are set to automatic. Engineering is currently investigating the issue. Upon investigation, Okta determined that a subset of customers on US Cell 3 who imported groups to Okta from Workday, Ultipro, or ServiceNow after 10am PST experienced a loss of group membership status for some users after import.\r\n\r\nIn cases where group membership was tied to provisioning for downstream applications, the loss of group memberships also removed user access to those applications. Our next update will be in an hour or sooner if additional information becomes available.
Apartments For Rent In Ho Chi Minh City,
Aircraft Mechanic Jobs In Netherlands,
Tripactions Resources,
Articles O