tdzjx (tdzjx) asked a question.
Hi team,
Can someone please share how I can obtain credentials for Okta Support should I need to create support cases?
I will post my question here as my team is currently monitoring the Okta endpoint: https://secure.duuo.ca/api/v1/users?activate=true. On occasions, not happening daily, since last year July 2023 we receive triggered alerts stating "503: Service Unavailable". Most recent was yesterday at 1:15pm. Can someone share if there has been any issues on your end at the infra level or other? Any blocked IPs, maybe as an example? Below is some details to the 503 error.
Details:
"<HTML><HEAD>\n<TITLE>Service Unavailable</TITLE>\n</HEAD><BODY>\n<H1>Service Unavailable - Zero size object</H1>\nThe server is temporarily unable to service your request. Please try again\nlater.<P>\nReference&*32;&*35;15&*46;ad95df17&*46;1705947317&*46;16e4ff17\n</BODY></HTML>\n",
"resolvedIps": [
"23.205.255.201",
"23.205.255.197"
],
"healthStatusCode": 6,
"healthStatus": "INVALID_CODE",
"responseMessage": "Service Unavailable",
"peerCertificateDetails": "[\n[\n Version: V3\n Subject: CN=duuo.ca, O=The Co-operators Group Limited, L=Regina, ST=Saskatchewan, C=CA\n Signature Algorithm: SHA256withRSA, OID = 1.2.840.113549.1.1.11\n\n Key: Sun EC public key, 256 bits\n public x coord: 70695039935992821000593981452214961812038776166529931988156702692062324075553\n public y coord: 37854254837240244857912121020269116918762808920735945279441820783819631968047\n parameters: secp256r1 [NIST P-256,X9.62 prime256v1] (1.2.840.10045.3.1.7)\n Validity: [From: Sun Jan 14 00:00:00 UTC 2024,\n To: Tue Jan 14 23:59:59 UTC 2025]\n Issuer: EMAILADDRESS=enterprise_network_services@cooperators.ca, CN=PaloAlto-IPS, OU=ENS, O=CGL, L=IDC, ST=Ontario, C=CA\n SerialNumber: [ 5d642798 52a0ea59 4af6695c ab120d6d]\n\nCertificate Extensions: 5\n[1]: ObjectId: 2.5.29.19 Criticality=true\nBasicConstraints:[\n CA:false\n PathLen: undefined\n]\n\n[2]: ObjectId: 2.5.29.37 Criticality=false\nExtendedKeyUsages [\n serverAuth\n clientAuth\n]\n\n[3]: ObjectId: 2.5.29.15 Criticality=true\nKeyUsage [\n DigitalSignature\n Key_Agreement\n]\n\n[4]: ObjectId: 2.5.29.17 Criticality=false\nSubjectAlternativeName [\n DNSName: duuo.ca\n DNSName: api.duuo.ca\n DNSName: app.duuo.ca\n DNSName: cooperators.duuo.ca\n DNSName: dashboard.duuo.ca\n DNSName: event.duuo.ca\n DNSName: fordinsure.cooperators.duuo.ca\n DNSName: lmcinsure.cooperators.duuo.ca\n DNSName: partnerships.duuo.ca\n DNSName: sandbox.duuo.ca\n DNSName: secure.duuo.ca\n]\n\n[5]: ObjectId: 2.5.29.14 Criticality=false\nSubjectKeyIdentifier [\nKeyIdentifier [\n0000: 23 6F 70 A7 4F D0 C8 D2 07 FA D0 36 E8 84 F3 21 *op.O......6...!\n0010: 26 DC 05 2D &..-\n]\n]\n\n]\n Algorithm: [SHA256withRSA]\n Signature:\n0000: 27 F2 40 85 73 41 1C 6F 49 CA F9 2F AF FA AA 77 '.@.sA.oI../...w\n0010: B4 7C D0 E9 B9 E4 36 9F 67 FD 5B 0D 1D 1D 08 95 ......6.g.[.....\n0020: FB F7 68 F2 93 AF 2B 07 D0 C0 05 8E BC C7 6E 2F ..h...+.......n/\n0030: 3D B2 A2 8B 3F F9 0F 2A 66 DB AD 86 7B A3 B6 A6 =...?..*f.......\n0040: 3E 59 27 67 A4 F7 99 D8 16 99 4A 24 97 34 1A 33 >Y'g......J$.4.3\n0050: B0 BB 59 7D 5D 76 79 0D 8D 47 A9 D7 BA 80 68 94 ..Y.]vy..G....h.\n0060: 3E 7C E5 29 FF E8 76 58 C4 CF 70 B9 31 D3 6A 16 >..)..vX..p.1.j.\n0070: 4B 76 07 EA 3E BA 8F 2B 8A 20 39 78 E5 12 54 BD Kv..>..+. 9x..T.\n0080: E2 35 B4 75 A5 9C CA 6C 27 F8 5C AE 2C 2E B4 98 .5.u...l'.\\.,...\n0090: D4 6B CB FE C4 FB 19 3F 74 C3 51 59 D9 7A 02 B2 .k.....?t.QY.z..\n00A0: 1A F9 CD 0A D5 0E 25 4D DF D9 46 33 EA E6 5F 31 ......%M..F3.._1\n00B0: 62 CF 2F EB FC 5F 6F 5D 2A B8 BA F8 01 AA FA 20 b./.._o]*...... \n00C0: 05 60 DC 17 22 0A 13 60 7A E2 BC 55 31 31 41 0D .`..\"..`z..U11A.\n00D0: 72 28 8B 90 E4 CA A5 D3 03 74 C6 A3 7D 95 BF E2 r(.......t......\n00E0: 81 B8 B6 7D 92 44 A5 A7 12 84 D7 BB 4F 20 92 24 .....D......O .$\n00F0: AC DF 52 62 12 F0 75 5A 98 44 65 D3 BC 1F 37 2B ..Rb..uZ.De...7+\n\n]",
"responseStatusCode": 503,
"totalTimeInMs": 763,
"responseSizeInBytes": 274,
"responseBodySizeLimitExceeded": false,
"hostnameResolutionTimeInMs": 150,
"tcpConnectTimeInMs": 2,
"tlsHandshakeTimeInMs": 7,
"timeToFirstByteInMs": 763,
"redirectsCount": 0,
"redirectionTimeInMs": 0,
"peerCertificateExpiryDate": 1736899199000,
"failureMessage": "",
"waitingTime": 604,
"customLogs": [],
"processingMode": "NONE"
We just want to understand what the root cause may be here.
Hello @tdzjx (tdzjx) Thank you for reacting out to our Community!
In order to open a case with Support you need to be an admin on Okta side, then once added as an Administrator you can open a case with Support from the Okta Help Center.
I have looked internally and there does not seem to be any issues with the service.
If you are looking for an root cause for that error, I would recommend to reach out to Support.
For Okta Staus, you can review if there are any incidents here:
https://status.okta.com/#recent
Community members help others by clicking Like or Select as Best on responses. Try it today.
Earn Today: New Okta Community Badges Have Arrived
Ask the Experts: Now Thru 1/31 Okta FastPass Engineering and Product Teams Answer Your Questions