Identity & access
AvailableOkta
By Okta
Imports users and groups from your Okta org into Qorionix IAM with incremental sync by lastUpdated, read-only. Sign-in with Okta as an external SAML or OIDC identity provider, inbound SCIM provisioning from Okta, and parsing Okta's system log through a relay are configured on their own screens and appear as capabilities of this same row.
What you can connect
Capabilities and availability
Each capability has its own setup and status. Review the details before enabling it for your organisation.
Directory sync
AvailableSetup available in the console
federated login
AvailableSetup available in the console
Inbound SCIM
AvailableSetup available in the console
Log collection
BetaSetup available in the console
Okta system-log events are parsed when they reach the HTTP Event Collector receiver from a relay such as Fluent Bit or Vector; Okta's built-in Log Streaming only targets Splunk Cloud hostnames and cannot be pointed here, and there is no polling connector.
What to know before connecting
Okta system-log events are parsed when they reach the HTTP Event Collector receiver from a relay such as Fluent Bit or Vector; Okta's built-in Log Streaming only targets Splunk Cloud hostnames and cannot be pointed here, and there is no polling connector.
More in Identity & access
Identity & access
AWS IAM (direct)
Imports IAM users, roles and groups from an AWS account into Qorionix IAM, read-only, so identity visibility covers accounts where AWS IAM is the directory of record rather than an upstream SSO provider. Does not manage IAM: no user, role or policy changes.
Identity & access
Active Directory / LDAP (direct)
Imports users and groups from an on-premises Active Directory or LDAPv3 directory into Qorionix IAM, read-only, over a direct LDAP bind and paged search. For tenants already synchronized to Microsoft Entra ID, the Entra ID directory sync integration is the better path.
Identity & access
Active Directory Federation Services (AD FS)
Sign in to Qorionix with on-premises Active Directory accounts through an AD FS farm acting as the SAML 2.0 identity provider. Directory contents stay on premises; only sign-in assertions cross.