Skip to main content
1Kosmos BlockID is a passwordless identity provider. Connect a 1Kosmos community to Oleria to see every user in the directories you choose, which users hold AdminX administrator roles, and who signed in, was locked out, or had their role changed.

​
What Oleria discovers

Once connected, Oleria continuously discovers the following from your 1Kosmos community:
  • Users - every user in each directory you list on the connection form (the built-in 1Kosmos directory, and Active Directory, LDAP, or Microsoft Entra ID directories connected to 1Kosmos). Disabled, locked, and inactive users show as disabled.
  • Roles - the AdminX roles: Basic User, Helpdesk Administrator, Community Administrator, and any custom roles your users hold.
  • Role membership - the AdminX role of each user.
  • Administrators - every user with an AdminX role other than Basic User, including custom roles, since each of them can sign in to the AdminX administration portal.
  • Activity - identity events from the 1Kosmos event log, including sign-ins, failed sign-ins, sign-ins to applications that use 1Kosmos for single sign-on, account lockouts, password resets, role changes, revoked sessions, device enrollment, and administrator changes to directories, the identity provider configuration, and authentication journeys.

​
Prerequisites

  • A 1Kosmos Community Administrator who can see Directory Integrations in AdminX.
  • Your tenant URL - the address of your AdminX portal, for example https://acme.1kosmos.net. Only addresses ending in .1kosmos.net are accepted.
  • Your community name. Most tenants have a single community named default.
  • A license key for your community that can call the 1Kosmos User Management and Reports APIs. If you don’t have one, ask your 1Kosmos administrator or your 1Kosmos account team for an API license key for the community.
  • The ID of each directory whose users you want Oleria to discover.

​
Find your directory IDs

1Kosmos doesn’t let integrations list a community’s directories, so you enter them on the connection form.
1

Open Directory Integrations

Sign in to AdminX as a Community Administrator and open Directory Integrations.
2

Copy each directory ID

For every directory whose users you want Oleria to see, copy its ID (for example 68418b901ac4790f690ffdb4). Include the built-in 1Kosmos directory if your users are stored there.
Oleria only discovers users in the directories you list. If you add a directory to 1Kosmos later, edit the integration and add its ID. If you remove a directory from 1Kosmos, also remove its ID from the integration: until you do, syncs fail with an error naming the directory, rather than reporting its users as removed.

​
Connect 1Kosmos to Oleria

1

Open the integration

Sign in to your Oleria workspace, navigate to Integrations, and select 1Kosmos.
2

Complete the connection form

3

Authenticate

Select Authenticate to validate and save the integration. Oleria looks up your community, then reads one user from every directory you listed. If 1Kosmos doesn’t recognize a directory ID, the error names it. If the license key can’t read the event log, the integration still connects and syncs users and roles without activity.

​
Verify the integration

Confirm the 1Kosmos instance appears on the Connected tab of your Oleria Integrations page with a status of Healthy. After the first sync completes, review the discovered users, roles, and activity in your Oleria workspace.

​
Remediation actions

This integration doesn’t support remediation actions. 1Kosmos doesn’t offer an API to disable, lock, or change the role of a user, so make those changes in AdminX.

​
Known limitations

  • Only the directories you list are discovered. 1Kosmos has no API that lists a community’s directories.
  • MFA and SSO requirements aren’t shown per user. 1Kosmos doesn’t report which authenticators a user has enrolled, so Oleria reports these as unavailable. Device enrollment and removal still appear as activity.
  • Groups aren’t synced. 1Kosmos doesn’t offer an API for groups. Connect the source directory to Oleria to see group membership.
  • Custom role permissions aren’t shown. A custom AdminX role appears by name. Its users are shown as administrators, because every role other than Basic User can sign in to AdminX.
  • Applications aren’t synced. Sign-ins to applications that use 1Kosmos for single sign-on appear as activity, with the application name.
  • Some activity may not be linked to a user. 1Kosmos identifies users in its event log by username. When two directories contain the same username and the event doesn’t say which directory it came from, the activity is shown without a linked user. Administrator changes (such as a role change or a lockout) whose event doesn’t name the administrator show the affected account but not who made the change.
  • Activity covers the last 90 days. The first sync reads up to 90 days of events.

​
Contact us

For questions about this integration, contact us at support@oleria.com.