{"id":9786,"date":"2026-04-29T10:05:29","date_gmt":"2026-04-29T08:05:29","guid":{"rendered":"https:\/\/www.idstory.com\/?p=9786"},"modified":"2026-04-29T10:50:37","modified_gmt":"2026-04-29T08:50:37","slug":"integrace-vema-identity-management","status":"publish","type":"post","link":"https:\/\/www.idstory.com\/cs\/integrace-vema-identity-management\/","title":{"rendered":"Integrace syst\u00e9mu Vema do Identity Manageru IdStory"},"content":{"rendered":"

Tento \u010dl\u00e1nek shrnuje zku\u0161enost z v\u00edce integra\u010dn\u00edch projekt\u016f syst\u00e9mu Vema do Identity Manageru IdStory. Zku\u0161enosti poch\u00e1zej\u00ed jak z mezin\u00e1rodn\u00edch holdingov\u00fdch spole\u010dnost\u00ed, tak z organizac\u00ed s tis\u00edci zam\u011bstnanci v jedn\u00e9 zemi. Popsan\u00e9 situace, probl\u00e9my a \u0159e\u0161en\u00ed vych\u00e1zej\u00ed z re\u00e1ln\u00fdch nasazen\u00ed v r\u016fzn\u00fdch prost\u0159ed\u00edch.<\/span><\/i><\/p>\n

V\u00fdchoz\u00ed stav<\/strong><\/h1>\n

P\u0159edstavte si organizaci, kter\u00e1 \u0159e\u0161\u00ed spr\u00e1vu identit ve v\u011bt\u0161\u00edm m\u011b\u0159\u00edtku. M\u016f\u017ee to b\u00fdt mezin\u00e1rodn\u00ed holding s des\u00edtkami dce\u0159in\u00fdch spole\u010dnost\u00ed a region\u00e1ln\u00edch pracovi\u0161\u0165, nebo jedin\u00e1 organizace s tis\u00edci zam\u011bstnanci a n\u011bkolika pobo\u010dkami. V obou p\u0159\u00edpadech ka\u017ed\u00fd m\u011bs\u00edc nastupuj\u00ed des\u00edtky a\u017e stovky nov\u00fdch koleg\u016f, doch\u00e1z\u00ed k vnit\u0159n\u00edm p\u0159esun\u016fm a ukon\u010den\u00ed pracovn\u00edch pom\u011br\u016f. P\u0159ed zaveden\u00edm IdM prob\u00edhala v\u00fdm\u011bna informac\u00ed mezi person\u00e1ln\u00edm a IT odd\u011blen\u00edm pomoc\u00ed e-mail\u016f, ticket\u016f v service desku a tabulek. Tento zp\u016fsob p\u0159in\u00e1\u0161el hned n\u011bkolik probl\u00e9m\u016f. Vznikaly chyby v u\u017eivatelsk\u00fdch jm\u00e9nech. Zam\u011bstnanci zdlouhav\u011b \u010dekali na p\u0159\u00edstupy do syst\u00e9m\u016f. A v neposledn\u00ed \u0159ad\u011b p\u0159edstavovaly bezpe\u010dnostn\u00ed riziko tzv. mrtv\u00e9 \u00fa\u010dty, kter\u00e9 z\u016fst\u00e1valy v syst\u00e9mech i po odchodu zam\u011bstnance. V naprost\u00e9 v\u011bt\u0161in\u011b p\u0159\u00edpad\u016f se p\u0159\u00edstupy \u0159e\u0161\u00ed prim\u00e1rn\u011b do MS Active Directory.<\/span><\/p>\n

IT t\u00fdm b\u00fdv\u00e1 zahlcen rutinn\u00ed administrativou, zat\u00edmco organizace postr\u00e1d\u00e1 jednotn\u00fd p\u0159ehled o identit\u00e1ch. Nasazen\u00ed Identity Manageru (IdM) IdStory a jeho napojen\u00ed na person\u00e1ln\u00ed syst\u00e9m Vema m\u011bn\u00ed tento proces v pln\u011b automatizovan\u00fd, bezpe\u010dn\u00fd a transparentn\u00ed tok dat.<\/span><\/p>\n

Kontext a c\u00edle implementace<\/strong><\/h1>\n

V kontextu napojen\u00ed syst\u00e9mu Vema do IdM se typicky jedn\u00e1 o n\u00e1sleduj\u00edc\u00ed c\u00edle. Hlavn\u00edm z nich je zprovoznit Vemu jako autoritativn\u00ed zdroj pravdy v IdM pro ve\u0161ker\u00e9 intern\u00ed zam\u011bstnance a extern\u00ed pracovn\u00edky (pokud jsem ve Vema evidov\u00e1ni) a nav\u00e1zat na ni automatizovan\u00fd provisioning do koncov\u00fdch syst\u00e9m\u016f. Mezi dal\u0161\u00ed kl\u00ed\u010dov\u00e9 po\u017eadavky pat\u0159\u00ed:<\/span><\/p>\n

    \n
  • Automatizace \u017eivotn\u00edho cyklu identit: Od vzniku pracovn\u00edho pom\u011bru p\u0159es zm\u011bny pozic a\u017e po okam\u017eit\u00fd offboarding.<\/span><\/li>\n
  • Konsolidace v\u00edce instanc\u00ed: Sjednocen\u00ed dat z r\u016fzn\u00fdch pobo\u010dek a dce\u0159in\u00fdch spole\u010dnost\u00ed pod centr\u00e1ln\u00ed spr\u00e1vu.<\/span><\/li>\n
  • Ochrana osobn\u00edch \u00fadaj\u016f: Zaji\u0161t\u011bn\u00ed souladu s bezpe\u010dnostn\u00edmi standardy p\u0159i nakl\u00e1d\u00e1n\u00ed s citliv\u00fdmi identifik\u00e1tory.<\/span><\/li>\n
  • Spr\u00e1va \u010dasov\u00fdch \u0159ez\u016f: Schopnost syst\u00e9mu reagovat na budouc\u00ed n\u00e1stupy a historick\u00e9 zm\u011bny \u00favazk\u016f.<\/span><\/li>\n
  • Univerz\u00e1lnost nasazen\u00ed: Pokryt\u00ed jak on-premise, tak cloudov\u00fdch instalac\u00ed syst\u00e9mu Vema.<\/span><\/li>\n<\/ul>\n

    Architektura \u0159e\u0161en\u00ed<\/strong><\/h1>\n

    Architektonick\u00fd n\u00e1vrh vyu\u017e\u00edv\u00e1 model datab\u00e1zov\u00e9ho v\u00fdm\u011bn\u00edku, kter\u00fd zaji\u0161\u0165uje izolaci person\u00e1ln\u00edho syst\u00e9mu od IdM platformy a stabilitu synchronizac\u00ed. Stejn\u00e1 architektura funguje pro on-premise i cloudovou Vemu, m\u011bn\u00ed se pouze zp\u016fsob, jak\u00fdm exportn\u00ed vrstva data z\u00edsk\u00e1v\u00e1.<\/span><\/p>\n

      \n
    • Exportn\u00ed vrstva: Specializovan\u00e9 Python skripty funguj\u00ed jako most mezi zdrojem dat a v\u00fdm\u011bn\u00edkem. U on-premise instalac\u00ed \u010dtou data z lok\u00e1ln\u00edho \u00falo\u017ei\u0161t\u011b Vema, u cloudov\u00e9 Vemy se p\u0159ipojuj\u00ed p\u0159\u00edmo k cloudov\u00e9 instanci a stahuj\u00ed data odtud. V\u00fdsledek je v obou p\u0159\u00edpadech stejn\u00fd: data v tabulk\u00e1ch v\u00fdm\u011bn\u00edku v jednotn\u00e9m tvaru.<\/span><\/li>\n
    • Mezivrstva (V\u00fdm\u011bn\u00edk): Rela\u010dn\u00ed datab\u00e1ze (MS SQL nebo PostgreSQL), ve kter\u00e9 datab\u00e1zov\u00e9 view sjednocuj\u00ed form\u00e1ty a transformuj\u00ed data z HR syst\u00e9mu do podoby, kterou o\u010dek\u00e1v\u00e1 IdM.<\/span><\/li>\n
    • Konektorov\u00e1 vrstva: IdM se p\u0159ipojuje k v\u00fdm\u011bn\u00edku pomoc\u00ed standardizovan\u00e9ho datab\u00e1zov\u00e9ho rozhran\u00ed (ConnId Database Table konektor vyu\u017e\u00edvaj\u00edc\u00ed JDBC), kter\u00e9 zaji\u0161\u0165uje pravideln\u00e9 na\u010d\u00edt\u00e1n\u00ed identit, organiza\u010dn\u00edch struktur a pracovn\u00edch vztah\u016f.<\/span><\/li>\n<\/ul>\n

      \"\"<\/p>\n

      Implementace<\/strong><\/h1>\n

      Mapov\u00e1n\u00ed dat z Vemy<\/strong><\/h2>\n

      \u017d\u00e1dn\u00e9 dv\u011b nasazen\u00ed Vemy nejsou identick\u00e1. Ka\u017ed\u00e1 organizace m\u00e1 syst\u00e9m nakonfigurov\u00e1n podle sv\u00fdch intern\u00edch pravidel a pou\u017e\u00edv\u00e1 i r\u016fzn\u00ed tabulky, a proto p\u0159ed vlastn\u00ed integrac\u00ed prov\u00e1d\u00edme anal\u00fdzu zdrojov\u00fdch dat. Spole\u010dn\u011b s person\u00e1ln\u00edm a IT odd\u011blen\u00edm z\u00e1kazn\u00edka identifikujeme, kde jsou v konkr\u00e9tn\u00ed instanci ulo\u017eeni zam\u011bstnanci a extern\u00ed pracovn\u00edci, kde jsou pracovn\u00ed vztahy a \u00favazky a jak je modelov\u00e1na organiza\u010dn\u00ed struktura. Tento krok ur\u010duje, co bude exportn\u00ed vrstva \u010d\u00edst a jak\u00fdm zp\u016fsobem se data p\u0159evedou do tabulek v\u00fdm\u011bn\u00edku. Bez spr\u00e1vn\u00e9ho mapov\u00e1n\u00ed by IdM dost\u00e1val ne\u00fapln\u00e1 nebo zkreslen\u00e1 data a cel\u00e1 automatizace by st\u00e1la na vratk\u00e9m z\u00e1kladu.<\/span><\/p>\n

      Podpora on-premise i cloudov\u00e9 Vemy<\/strong><\/h2>\n

      \u0158e\u0161en\u00ed podporuje ob\u011b varianty nasazen\u00ed Vemy. Pokud m\u00e1 \u010d\u00e1st pobo\u010dek on-premise a \u010d\u00e1st v cloudu, oba zdroje se sb\u00edhaj\u00ed do t\u00e9ho\u017e v\u00fdm\u011bn\u00edku a do IdM p\u0159ich\u00e1zej\u00ed jako jednotn\u00fd datov\u00fd tok.<\/span><\/p>\n

      V prost\u0159ed\u00edch, kde organizace provozuje des\u00edtky dce\u0159in\u00fdch spole\u010dnost\u00ed a des\u00edtky instanc\u00ed Vemy, je v\u00fdhodn\u00e9, \u017ee z\u00e1kazn\u00edk si \u010dasem dok\u00e1\u017ee napojov\u00e1n\u00ed dal\u0161\u00edch spole\u010dnost\u00ed spravovat s\u00e1m. Prvn\u00ed vlnu integrac\u00ed realizujeme spole\u010dn\u011b se z\u00e1kazn\u00edkem. Postupn\u011b, jak si intern\u00ed t\u00fdm projde proces u n\u011bkolika spole\u010dnost\u00ed, z\u00edsk\u00e1v\u00e1 praktickou znalost mapov\u00e1n\u00ed dat, konfigurace exportn\u00ed vrstvy i logiky v\u00fdm\u011bn\u00edku. Po n\u011bkolika spole\u010dn\u011b odveden\u00fdch napojen\u00edch je t\u00fdm schopen roz\u0161i\u0159ovat \u0159e\u0161en\u00ed o dal\u0161\u00ed spole\u010dnosti vlastn\u00edmi silami. T\u00edm se v\u00fdrazn\u011b zkracuje doba pot\u0159ebn\u00e1 k za\u0159azen\u00ed nov\u011b akv\u00edrovan\u00fdch nebo nov\u011b vznikl\u00fdch subjekt\u016f pod centr\u00e1ln\u00ed spr\u00e1vu identit a kles\u00e1 z\u00e1vislost na dodavateli.<\/span><\/p>\n

      Logika hlavn\u00edho \u00favazku<\/strong><\/h2>\n

      Kl\u00ed\u010dov\u00fdm prvkem implementace je logika ur\u010dov\u00e1n\u00ed hlavn\u00edho \u00favazku. V prost\u0159ed\u00edch s v\u00edce soub\u011b\u017en\u00fdmi smlouvami IdM automaticky vyhodnocuje prioritu \u00favazku na z\u00e1klad\u011b typu pracovn\u00edho vztahu, funk\u010dn\u00edho za\u0159azen\u00ed nebo explicitn\u00edch p\u0159\u00edznak\u016f z HR syst\u00e9mu. Tato logika \u0159\u00edd\u00ed generov\u00e1n\u00ed prim\u00e1rn\u00edho loginu, e-mailov\u00e9 adresy, ur\u010duje organiza\u010dn\u00ed za\u0159azen\u00ed a p\u0159i\u0159azen\u00e1 opr\u00e1vn\u011bn\u00ed v Active Directory.<\/span><\/p>\n

      Bezpe\u010dnost citliv\u00fdch dat<\/strong><\/h2>\n

      Pro zaji\u0161t\u011bn\u00ed maxim\u00e1ln\u00ed bezpe\u010dnosti jsou citliv\u00e9 osobn\u00ed \u00fadaje u\u017eivatel\u016f hashov\u00e1ny ji\u017e p\u0159i v\u00fdstupu z HR syst\u00e9mu. IdM tak pracuje pouze s unik\u00e1tn\u00edmi otisky, kter\u00e9 umo\u017e\u0148uj\u00ed korelaci identit nap\u0159\u00ed\u010d syst\u00e9my, ani\u017e by doch\u00e1zelo k ukl\u00e1d\u00e1n\u00ed ne\u0161ifrovan\u00fdch citliv\u00fdch dat v integra\u010dn\u00ed vrstv\u011b.<\/span><\/p>\n

      Probl\u00e9my a jejich \u0159e\u0161en\u00ed<\/strong><\/h1>\n

      P\u0159i n\u00e1vrhu integrace bylo t\u0159eba proaktivn\u011b o\u0161et\u0159it n\u011bkolik typick\u00fdch rizik, kter\u00e1 se v podobn\u00fdch projektech opakuj\u00ed. Bez jejich \u0159e\u0161en\u00ed by IdM v provozu nar\u00e1\u017eel na situace, ve kter\u00fdch by data nebyla konzistentn\u00ed nebo by automatizace selh\u00e1vala v okrajov\u00fdch p\u0159\u00edpadech.<\/span><\/p>\n

      Kolize identifik\u00e1tor\u016f<\/strong><\/h2>\n

      V multispole\u010dnostn\u00edm prost\u0159ed\u00ed by doch\u00e1zelo k p\u0159ekryv\u016fm v \u010d\u00edseln\u00fdch \u0159ad\u00e1ch organiza\u010dn\u00edch \u00fatvar\u016f, proto\u017ee jednotliv\u00e9 pobo\u010dky pou\u017e\u00edvaj\u00ed vlastn\u00ed, na sob\u011b nez\u00e1visl\u00e9 \u010d\u00edslov\u00e1n\u00ed. Stejn\u00fd k\u00f3d \u00fatvaru tak m\u016f\u017ee existovat sou\u010dasn\u011b v n\u011bkolika spole\u010dnostech a syst\u00e9m by je nedok\u00e1zal jednozna\u010dn\u011b odli\u0161it.<\/span><\/p>\n

      \u0158e\u0161en\u00edm je dynamick\u00e9 dopl\u0148ov\u00e1n\u00ed prefix\u016f ke k\u00f3d\u016fm organiza\u010dn\u00edch jednotek. Ka\u017ed\u00fd \u00fatvar z\u00edsk\u00e1 p\u0159ed sv\u016fj p\u016fvodn\u00ed k\u00f3d identifik\u00e1tor konkr\u00e9tn\u00ed pobo\u010dky \u010di spole\u010dnosti, \u010d\u00edm\u017e je nap\u0159\u00ed\u010d cel\u00fdm prost\u0159ed\u00edm zaji\u0161t\u011bna jednozna\u010dnost. V\u00fdhodou tohoto p\u0159\u00edstupu je, \u017ee z\u00e1kazn\u00edk nemus\u00ed m\u011bnit zaveden\u00e9 \u010d\u00edseln\u00e9 \u0159ady ve sv\u00fdch HR ani lok\u00e1ln\u00edch syst\u00e9mech. Prefixy se p\u0159id\u00e1vaj\u00ed automaticky a\u017e v mezivrstv\u011b.<\/span><\/p>\n

      Aktivace budouc\u00edch zm\u011bn<\/strong><\/h2>\n

      Standardn\u00ed p\u0159\u00edr\u016fstkov\u00e1 synchronizace kontrakt\u016f reaguje pouze na zm\u011bny proveden\u00e9 v HR syst\u00e9mu. Probl\u00e9m by ale nastal u zam\u011bstnanc\u016f, jejich\u017e n\u00e1stup je v HR zaevidov\u00e1n s p\u0159edstihem, nap\u0159\u00edklad n\u011bkolik t\u00fddn\u016f dop\u0159edu. HR syst\u00e9m v den re\u00e1ln\u00e9ho n\u00e1stupu \u017e\u00e1dnou novou zm\u011bnu neprovede, tak\u017ee synchronizace by nem\u011bla co p\u0159en\u00e9st a IdM by zam\u011bstnance v den D automaticky neaktivoval. Nov\u00fd kolega by tak prvn\u00ed den v pr\u00e1ci nem\u011bl p\u0159\u00edstupy do syst\u00e9m\u016f.<\/span><\/p>\n

      Proto je v \u0159e\u0161en\u00ed od za\u010d\u00e1tku zapojena funkce \u010dasov\u00fdch \u0159ez\u016f pro kontrakty. IdM ka\u017ed\u00fd den nez\u00e1visle na ud\u00e1lostech v HR projde v\u0161echny evidovan\u00e9 \u010dasov\u00e9 \u0159ezy kontrakt\u016f, zkontroluje jejich aktu\u00e1ln\u00ed platnost a p\u0159epo\u010dte kontrakty. Pokud m\u00e1 n\u011bkdo k dan\u00e9mu dni za\u010d\u00edt pracovat, syst\u00e9m to s\u00e1m rozpozn\u00e1 a automaticky aktivuje jeho \u00fa\u010dty a p\u0159\u00edstupy. Stejn\u00fd mechanismus spolehliv\u011b zachyt\u00ed i konce kontrakt\u016f, zm\u011bny \u00favazk\u016f nebo do\u010dasn\u00e9 pozastaven\u00ed.<\/span><\/p>\n

      Spr\u00e1va log\u016f<\/strong><\/h2>\n

      Provoz v\u00fdm\u011bn\u00edku generuje velk\u00e9 mno\u017estv\u00ed datab\u00e1zov\u00fdch transakc\u00ed, proto\u017ee synchronizace mezi HR syst\u00e9mem a IdM prob\u00edh\u00e1 \u010dasto a v pln\u00e9m rozsahu. Ka\u017ed\u00e1 zm\u011bna se zapisuje do transak\u010dn\u00edho logu datab\u00e1ze, kter\u00fd by bez spr\u00e1vn\u00e9ho nastaven\u00ed rostl rychleji, ne\u017e by se st\u00edhal \u010distit. V krajn\u00edm p\u0159\u00edpad\u011b by zapln\u011bn\u00ed logu vedlo k zastaven\u00ed datab\u00e1ze a t\u00edm i cel\u00e9 synchronizace identit.<\/span><\/p>\n

      \u0158e\u0161en\u00ed spo\u010d\u00edv\u00e1 ve dvou konfigura\u010dn\u00edch kroc\u00edch. Datab\u00e1ze v\u00fdm\u011bn\u00edku je provozov\u00e1na v takzvan\u00e9m jednoduch\u00e9m re\u017eimu obnovy (Simple recovery model), kter\u00fd automaticky uvol\u0148uje m\u00edsto v logu po dokon\u010den\u00ed ka\u017ed\u00e9 transakce a nezadr\u017euje celou historii zm\u011bn. Ta pro mezivrstvu tohoto typu nen\u00ed pot\u0159eba, proto\u017ee autoritativn\u00edm zdrojem dat z\u016fst\u00e1v\u00e1 HR syst\u00e9m, nikoli v\u00fdm\u011bn\u00edk. Z\u00e1rove\u0148 jsou nastaveny pevn\u00e9 limity pro maxim\u00e1ln\u00ed velikost logovac\u00edch soubor\u016f, co\u017e chr\u00e1n\u00ed datab\u00e1zi p\u0159ed neo\u010dek\u00e1van\u00fdm n\u00e1r\u016fstem a usnad\u0148uje kapacitn\u00ed pl\u00e1nov\u00e1n\u00ed.<\/span><\/p>\n

      Lessons learned<\/strong><\/h1>\n
        \n
      • Role v\u00fdm\u011bn\u00edku: Mezivrstva je kritick\u00e1 pro stabilitu cel\u00e9ho \u0159e\u0161en\u00ed. Umo\u017e\u0148uje IdM IdStory prov\u00e1d\u011bt datov\u00e9 \u00fapravy a \u010di\u0161t\u011bn\u00ed (o\u0159ez\u00e1n\u00ed mezer na za\u010d\u00e1tku a konci hodnot) bez nutnosti zasahovat do nastaven\u00ed person\u00e1ln\u00edho syst\u00e9mu.<\/span><\/li>\n
      • UX pro spr\u00e1vce: Automatick\u00e9 sestaven\u00ed stromov\u00e9 struktury pracovi\u0161\u0165 v IdM na z\u00e1klad\u011b dat z Vemy v\u00fdrazn\u011b zvy\u0161uje p\u0159ehlednost a usnad\u0148uje administr\u00e1tor\u016fm p\u0159id\u011blov\u00e1n\u00ed aplika\u010dn\u00edch rol\u00ed.<\/span><\/li>\n
      • Konzistence dat: Modelov\u00e1n\u00ed kontrakt\u016f jako \u010dasov\u00fdch \u0159ez\u016f v IdM je nezbytn\u00e9 pro spr\u00e1vn\u00e9 fungov\u00e1n\u00ed automatizovan\u00e9ho provisioningu do koncov\u00fdch syst\u00e9m\u016f, zejm\u00e9na u dop\u0159edn\u011b pl\u00e1novan\u00fdch person\u00e1ln\u00edch zm\u011bn.<\/span><\/li>\n
      • Samoobslu\u017en\u00e9 roz\u0161i\u0159ov\u00e1n\u00ed: U organizac\u00ed s des\u00edtkami instanc\u00ed Vemy je provozn\u011b v\u00fdhodn\u00e9, kdy\u017e si intern\u00ed t\u00fdm z\u00e1kazn\u00edka dok\u00e1\u017ee napojen\u00ed dal\u0161\u00edch spole\u010dnost\u00ed \u0159e\u0161it s\u00e1m. Tato schopnost p\u0159ich\u00e1z\u00ed postupn\u011b. Prvn\u00ed napojen\u00ed vedeme spole\u010dn\u011b, z\u00e1kazn\u00edk si proces osvoj\u00ed v praxi a po n\u011bkolika spole\u010dn\u011b odveden\u00fdch integrac\u00edch se posouv\u00e1 do role samostatn\u00e9ho provozovatele.<\/span><\/li>\n<\/ul>\n

        Z\u00e1v\u011br<\/strong><\/h1>\n

        Integrace person\u00e1ln\u00edho syst\u00e9mu Vema do Identity Manageru IdStory p\u0159inesla organizac\u00edm \u0159\u00e1d a automatizaci do spr\u00e1vy u\u017eivatelsk\u00fdch opr\u00e1vn\u011bn\u00ed. Odstran\u011bn\u00ed manu\u00e1ln\u00edch p\u0159epis\u016f dat zkr\u00e1tilo proces n\u00e1stupu zam\u011bstnance z dn\u016f na jednotky minut a garantuje okam\u017eit\u00e9 blokov\u00e1n\u00ed p\u0159\u00edstup\u016f p\u0159i odchodu.<\/span><\/p>\n

        D\u00edky podpo\u0159e on-premise i cloudov\u00e9 Vemy a mo\u017enosti z\u00e1kazn\u00edka samostatn\u011b roz\u0161i\u0159ovat \u0159e\u0161en\u00ed o dal\u0161\u00ed spole\u010dnosti je architektura p\u0159ipravena r\u016fst spolu s organizac\u00ed. Digit\u00e1ln\u00ed identita je nyn\u00ed p\u0159esn\u00fdm odrazem re\u00e1ln\u00e9ho stavu organizace, co\u017e zvy\u0161uje efektivitu pr\u00e1ce IT odd\u011blen\u00ed i celkovou bezpe\u010dnost informa\u010dn\u00edch syst\u00e9m\u016f.<\/span><\/p>\n

         <\/p>\n

        \u0158e\u0161\u00edte n\u011bco podobn\u00e9ho? Ozv\u011bte se n\u00e1m na sales@idstory.com<\/h3>\n

        <\/h3>\n","protected":false},"excerpt":{"rendered":"

        Tento \u010dl\u00e1nek shrnuje zku\u0161enost z v\u00edce integra\u010dn\u00edch projekt\u016f syst\u00e9mu Vema do Identity Manageru IdStory. Zku\u0161enosti poch\u00e1zej\u00ed jak z mezin\u00e1rodn\u00edch holdingov\u00fdch spole\u010dnost\u00ed, tak z organizac\u00ed s tis\u00edci zam\u011bstnanci v jedn\u00e9 zemi. Popsan\u00e9 situace, probl\u00e9my a \u0159e\u0161en\u00ed vych\u00e1zej\u00ed z re\u00e1ln\u00fdch nasazen\u00ed v r\u016fzn\u00fdch prost\u0159ed\u00edch. V\u00fdchoz\u00ed stav P\u0159edstavte si organizaci, kter\u00e1 \u0159e\u0161\u00ed spr\u00e1vu identit ve v\u011bt\u0161\u00edm m\u011b\u0159\u00edtku. M\u016f\u017ee […]<\/p>\n","protected":false},"author":15,"featured_media":9797,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"elementor_theme","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[27,32,34],"tags":[],"class_list":["post-9786","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-idstory","category-identity-manager","category-konektory"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/posts\/9786","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/comments?post=9786"}],"version-history":[{"count":0,"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/posts\/9786\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/media\/9797"}],"wp:attachment":[{"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/media?parent=9786"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/categories?post=9786"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.idstory.com\/cs\/wp-json\/wp\/v2\/tags?post=9786"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}