You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The org URL must be `https://<org>.okta.com` (or `oktapreview.com` / `okta-emea.com` / a custom domain), with no trailing slash and an `https://` scheme.
148
+
The org domain must be `<org>.okta.com` (or `.oktapreview.com` / `.okta-emea.com` / `.okta-gov.com`). Pass the bare hostname only — no `https://` scheme, no path, no trailing slash. Custom (vanity) domains are not currently accepted.
@@ -73,7 +73,7 @@ The private key file may contain either a PEM-encoded RSA key or a JWK JSON docu
73
73
For automated environments where writing the key to disk is not desirable (Prowler App, CI runners, container secrets, etc.), the private key may be passed directly as a string:
@@ -127,7 +127,7 @@ As new services and checks land in the Okta provider, the default scope list gro
127
127
128
128
### Common Errors
129
129
130
-
-**`OktaInvalidOrgURLError`** — the org URL must be `https://<org>.okta.com` (or `oktapreview.com` / `okta-emea.com`) with no trailing slash.
130
+
-**`OktaInvalidOrgDomainError`** — the org domain must be `<org>.okta.com` (or `.oktapreview.com` / `.okta-emea.com` / `.okta-gov.com`). Pass the bare hostname only — no `https://` scheme, no path, no trailing slash.
131
131
-**`OktaPrivateKeyFileError`** — confirm the file is readable and contains a non-empty PEM or JWK body.
132
132
-**`OktaInsufficientPermissionsError`** — the credential probe reached Okta but the service app cannot perform the request. The error string carries `invalid_scope`, `Forbidden`, `not authorized`, or `permission`. Fix by granting the missing `okta.*.read` scope from **Okta API Scopes** and confirming the **Read-Only Administrator** role is assigned to the service app.
133
133
-**`OktaInvalidCredentialsError`** — the credential probe reached Okta but Okta rejected the JWT. Typically the private key on disk does not match the public JWK uploaded to the service app, or the JWT signing parameters are wrong. Regenerate the keypair and re-upload the public JWK.
Copy file name to clipboardExpand all lines: prowler/providers/okta/exceptions/exceptions.py
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,9 @@ class OktaBaseException(ProwlerException):
22
22
"message": "Okta credentials are not valid",
23
23
"remediation": "Check the client ID and private key for the Okta service app.",
24
24
},
25
-
(14004, "OktaInvalidOrgURLError"): {
26
-
"message": "Okta organization URL is not valid",
27
-
"remediation": "Provide an org URL in the form https://<org>.okta.com (no trailing slash).",
25
+
(14004, "OktaInvalidOrgDomainError"): {
26
+
"message": "Okta organization domain is not valid",
27
+
"remediation": "Provide an Okta-managed domain such as <org>.okta.com (or .oktapreview.com / .okta-emea.com / .okta-gov.com), with no scheme and no trailing slash.",
28
28
},
29
29
(14005, "OktaPrivateKeyFileError"): {
30
30
"message": "Okta private key file could not be read",
0 commit comments