> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 1Password integratsiyasini sozlash

> 1Password Events API’ni Living Security bilan ulang: hisob, autentifikatsiya, ma’muriy harakatlar va hisob ma’lumotlari omboridagi faollik uchun.

export const PublicIntegrationNextSteps = () => <>
    <hr />
    <h2>Tegishli resurslar</h2>
    <ul>
      <li>
        <a href="/uz/signals/data-sources">Integrations ma'lumotlari Human Risk Management signallariga qanday aylanishini bilib oling</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/integrations">Living Security integratsiyalarini o'rganing</a>
      </li>
      <li>
        <a href="https://app.livingsecurity.ai/">Living Security Platform'ni oching</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/request-demo/">Living Security demosini so'rang</a>
      </li>
    </ul>
  </>;

export const ConnectInPlatform = ({tile, children}) => <Step title="Living Security Platform'da hisob ma'lumotlarini kiriting">
    <p>
      Living Security'ga kirish huquqiga ega bo'lgan shaxs — dastur egasi yoki (agar taklif qilingan bo'lsa)
      tizim administratori tomonidan bajariladi (topshirilgan sozlash).
    </p>
    <ol>
      <li>
        <strong>Settings → Integrations → Catalog</strong> bo'limiga o'ting, <strong>{tile}</strong>{' '}
        kartasini toping va <strong>Connect</strong> tugmasini bosing.
      </li>
      <li>
        Quyidagi maydonlarni to'ldiring, so'ng <strong>Connect</strong> tugmasini bosing.
      </li>
    </ol>
    {children}
  </Step>;

export const SystemAdminBanner = ({system, recommendDelegated}) => <Note>
    <p>
      <strong>Ushbu qo‘llanma {system} administratoriga mo‘ljallangan.</strong> Unda {system} ichida API
      hisob ma’lumotlarini yaratish tartibi bayon etilgan; buning uchun {system} tizimiga administrator
      sifatida kirish huquqi talab etiladi, Living Security Platform’ga esa talab etilmaydi.
    </p>
    <p>
      Agar siz Living Security’da <strong>dastur egasi</strong> bo‘lsangiz va {system} tizimini
      boshqarmasangiz, ushbu sahifani uni boshqaradigan shaxsga yuboring. U A qismini bajaradi va hisob ma’lumotlarini sizga qaytaradi
      (yoki agar siz uni platformaga taklif qilgan bo‘lsangiz, ularni bevosita o‘zi kiritadi).
      {recommendDelegated && <>
          {' '}Sozlash jarayonida maxfiy kalit ma’lumotlari hosil bo‘lgani uchun, maxfiy kalit sizga qayta yuborilmasligi uchun{' '}
          <strong>delegated setup</strong> usulidan foydalanishni tavsiya etamiz.
        </>}
    </p>
  </Note>;

<SystemAdminBanner system="1Password" recommendDelegated={true} />

## Ushbu integratsiya nimani taqdim etadi

1Password normallashtirilgan hisob, autentifikatsiya, ma’muriy harakatlar va hisob ma’lumotlari omboridagi faollik ma’lumotlarini taqdim etishi mumkin. Ko‘rib chiqilgan misollar quyidagilardan iborat:

* `mfa.factor.activated` — qo‘shimcha MFA omillarini faollashtiradi
* `credential.vault.created` — hisob ma’lumotlari omboriga yozuvlar qo‘shadi
* `credential.downloaded` — hisob ma’lumotlari eksport qilingan

[Integratsiya ma’lumotlari qanday qilib signals’ga aylanishi](/uz/signals/data-sources) bilan tanishing.

## Living Security uchun nimalar talab qilinadi

| Credential | Description |
| - | - |
| **Events API bearer token** | Events Reporting integratsiyasi uchun berilgan token. |
| **Events API host** | 1Password hisobingiz uchun host, masalan, `events.1password.com`. Faqat hostni kiriting. |

Tokenni berishda **sign-in attempts**, **item usages** va **audit events** uchun ruxsatni tanlang. Integratsiyani 1Password Business egasi yoki administratori yaratishi kerak.

## Sozlash

<Steps>
  <Step title="1Password’da Events Reporting integratsiyasini yarating">
    1Password veb-ilovasida **Integrations** bo‘limini oching, **Events Reporting** ni tanlang va **Other** uchun integratsiya qo‘shing. Unga **Living Security** kabi tanib olish oson nom bering.
  </Step>

  <Step title="Bearer token bering">
    Sign-in attempts, item usages va audit events’ni tanlang. Amal qilish muddatini hisob ma’lumotlarini almashtirish siyosatingizga mos ravishda belgilang, tokenni bering va uni xavfsiz joyda saqlang. 1Password tokenni faqat bir marta ko‘rsatadi.
  </Step>

  <ConnectInPlatform tile="1Password Events API">
    Events API hosti va bearer tokenni kiriting. Hostga `https://` yoki oxirgi slesh belgisini qo‘shmang.
  </ConnectInPlatform>
</Steps>

## Tekshirish va nosozliklarni bartaraf etish

Ulangandan so‘ng ulanish testi muvaffaqiyatli o‘tganini va birinchi sinxronizatsiya boshlanganini tekshiring. Tanlangan hodisa turlari bo‘yicha yaqinda faollik bo‘lmasa, muvaffaqiyatli ulanish dastlab nol yozuv haqida xabar berishi mumkin.

<AccordionGroup>
  <Accordion title="401 Unauthorized">
    Token yaroqsiz, muddati tugagan yoki bekor qilingan. Events Reporting integratsiyasidan yangi token bering va qayta ulang.
  </Accordion>

  <Accordion title="Events are missing">
    Tokenni tahrirlang yoki almashtiring hamda sign-in attempts, item usages va audit events tanlanganini tasdiqlang.
  </Accordion>

  <Accordion title="The host is rejected">
    Hisobingiz uchun Events API hostidan `https://` yoki oxirgi sleshsiz foydalaning. Mintaqaviy yoki korporativ muhitlar uchun host boshqacha bo‘lishi mumkin.
  </Accordion>
</AccordionGroup>

Vendor tomonidagi batafsil ma’lumot uchun [1Password’ning Events API sozlash qo‘llanmasi](https://www.1password.dev/events-api/get-started)ga qarang.

<PublicIntegrationNextSteps />


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.