> ## 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.

# OneLogin integratsiyasini sozlash

> OneLogin'ni foydalanuvchi hayot sikli, autentifikatsiya, MFA va ma’muriy faoliyat ma’lumotlari uchun Living Security bilan ulang.

export const EgressIpAllowlistBothSets = ({system}) => <Warning>
    <strong>{system} uchun bitta emas, ikki guruh manzil kerak.</strong> Living Security ushbu integratsiyaning kirish tokenini o‘z infratuzilmasida yaratadi va uni uzluksiz yangilab turadi, shu sababli sozlash trafigi va sinxronizatsiya trafigi turli tarmoqlardan chiqadi. Ikkala guruhni ham {system} tizimidagi ruxsat etilganlar ro‘yxatiga kiriting va ikkalasini ham saqlab qo‘ying — bu faqat sozlash bosqichiga tegishli talab emas.
    <br />
    <br />
    <strong>Integratsiya sinxronizatsiyasi trafigi</strong> — barcha mintaqalarda bir xil:
    <br />
    <code>52.34.139.153/32</code>, <code>54.69.127.183/32</code>, <code>44.247.133.183/32</code>,{' '}
    <code>52.26.211.56/32</code>
    <br />
    <br />
    <strong>Platforma trafigi</strong> — faqat tashkilotingiz joylashgan mintaqaga tegishli qatordan foydalaning:
    <br />
    AQSh: <code>98.91.60.249/32</code>, <code>13.216.91.102/32</code>
    <br />
    Yevropa Ittifoqi: <code>34.246.236.210/32</code>, <code>52.31.102.238/32</code>
    <br />
    <br />
    Faqat sinxronizatsiya guruhi ruxsat etilsa, sozlash hech qachon yakunlanmaydi. Faqat platforma guruhi ruxsat etilsa, sozlash muvaffaqiyatli bo‘ladi, ammo barcha sinxronizatsiyalar xato bilan tugaydi. Ikkala nosozlik belgilari va o‘zgartirish siyosati bo‘yicha{' '}
    <a href="/uz/integrations/managing/egress-ip-addresses">
      Configuring Integration Egress IP Addresses
    </a>{' '}
    bo‘limiga qarang.
  </Warning>;

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="OneLogin" recommendDelegated={true} />

## Ushbu integratsiya nimalarni taqdim etadi

OneLogin normallashtirilgan foydalanuvchi hayot sikli, autentifikatsiya, MFA va ma’muriy faoliyat ma’lumotlarini taqdim etishi mumkin. Ko‘rib chiqilgan misollar:

* `mfa.success` — MFA tekshiruvlarini muvaffaqiyatli yakunlaydi
* `mfa.failed` — MFA tekshiruvlaridan o‘ta olmaydi
* `account.locked` — hisob bloklangan

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

## Living Security uchun nima talab etiladi

| Credential | Description |
| - | - |
| **Client ID** | Foydalanuvchilar va hodisalarni o‘qish huquqiga ega bo‘lgan OneLogin API hisob ma’lumotlari juftligining client ID qiymati. |
| **Client secret** | Shu hisob ma’lumotlari juftligining client secret qiymati. |
| **Tenant subdomain** | OneLogin tenant URL manzilingizda `.onelogin.com` dan oldingi qiymat. |

## Sozlash

<Steps>
  <Step title="OneLogin'da API hisob ma’lumotlarini yaratish">
    Akkaunt egasi yoki administrator sifatida **Developers → API Credentials** bo‘limini oching, alohida hisob ma’lumotlarini yarating va foydalanuvchilar hamda hodisalarni o‘qiy oladigan scope’ni tanlang. Client ID va secret qiymatlarini xavfsiz joyda saqlang.
  </Step>

  <ConnectInPlatform tile="OneLogin">
    Tenant subdomain, client ID va client secret qiymatlarini kiriting, so‘ng ulanishni amalga oshiring.
  </ConnectInPlatform>
</Steps>

Living Security hisob ma’lumotlari juftligini access token’ga almashtiradi va uni muddati tugashidan oldin yangilab turadi, shuning uchun token yaratish yoki uni almashtirish talab etilmaydi. Hisob ma’lumotlari juftligining o‘zini odatdagi jadvalingiz bo‘yicha almashtiring va shundan keyin tile’ni qayta ulang.

## Tekshirish va nosozliklarni bartaraf etish

Ulanish kamida bitta foydalanuvchini o‘qiy olishini tekshiring. Tenantda yaqinda faoliyat bo‘lmasa, audit hodisalari bo‘sh bo‘lishi mumkin.

<AccordionGroup>
  <Accordion title="401 Unauthorized">
    Client ID yoki client secret noto‘g‘ri, yoki hisob ma’lumotlari juftligi OneLogin’da o‘chirib yuborilgan. Juftlik **Developers → API Credentials** bo‘limida hali mavjudligini tasdiqlang, so‘ng joriy qiymatlar bilan qayta ulaning.
  </Accordion>

  <Accordion title="403 Forbidden">
    API hisob ma’lumotlarini OneLogin resurs API’lari, foydalanuvchilar va hodisalarni o‘qish huquqi bilan qayta yarating.
  </Accordion>

  <Accordion title="Tenantga ulanib bo‘lmayapti">
    Faqat tenant subdomain qiymatini kiriting — to‘liq URL yoki ma’muriy ko‘rinadigan nomni emas.

    Subdomain to‘g‘ri bo‘lsa-yu, tenantga baribir ulanib bo‘lmasa, akkauntingizda OneLogin API’ga kirishni manba IP manzili bo‘yicha cheklab qo‘yganmi, tekshiring. Ushbu integratsiya uchun manzillarning **ikkita** to‘plami ruxsat etilganlar ro‘yxatiga kiritilishi kerak, chunki Living Security access token’ni o‘zi yaratadi va uni doimiy ravishda yangilab turadi — shu sababli token so‘rovlari va rejalashtirilgan sinxronlashlar turli tarmoqlardan yuboriladi.

    <EgressIpAllowlistBothSets system="OneLogin" />
  </Accordion>
</AccordionGroup>

Vendor tomonidagi batafsil ma’lumot uchun [OneLogin’ning API hisob ma’lumotlari bo‘yicha qo‘llanmasiga](https://developers.onelogin.com/api-docs/2/getting-started/working-with-api-credentials) qarang.

<PublicIntegrationNextSteps />


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