Project

General

Profile

Actions

Task #1854

closed

WF for synchronization groups/roles assing bad role catalogue

Added by Ondřej Kopr over 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Patrik Stloukal
Target version:
Start date:
09/16/2019
Due date:
% Done:

100%

Estimated time:
Owner:

Description

Please update behavior with putting roles into catalogue.

Use case:
  • project has these groups on AD:
    1: "CN=groupName001,OU=Confluence,OU=Groups,OU=Company001,DC=example,DC=tld" 
    2: "CN=groupName002,OU=Jira,OU=Groups,OU=Company001,DC=example,DC=tld" 
    3: "CN=groupName003,OU=Confluence,OU=Groups,OU=Company002,DC=example,DC=tld" 
    4: "CN=groupName004,OU=Confluence,OU=Groups,OU=Company003,DC=example,DC=tld" 
    5: "CN=groupName005,OU=Jira,OU=Groups,OU=Company004,DC=example,DC=tld" 
    ...
    
  1. In this step will be synchronizace groups number one (groupName001) and it will be created catalogues Company001, Groups, Confluence. This role has assigned correct role catalogue,
  2. in this step will be synchronizace groups number two (groupName002) and it will be created catalogue Jira. This role has also assigned correct role catalogue,
  3. in this step will be synchronizace groups number three (groupName003) and it will be created catalogue Company002. But this role will be assigned into role catalogue Confluence created in first step,
  4. in this step will be synchronizace groups number four (groupName004) and it will be created catalogue Company003. But this role will be also assigned into role catalogue Confluence created in first step,
  5. in this step will be synchronizace groups number five (groupName005) and it will be created catalogue Company004. But this role will be assigned into role catalogue Jira created in second step.

Result:

root
 ├── Company001                           
 |   └── Groups                           
 |       ├── Confluence
 |       |      (groupName001) - OK
 |       |      (groupName003) - NOT OK
 |       |      (groupName004) - NOT OK
 |       |
 |       └── Jira                      
 |              (groupName002) - OK
 |              (groupName005) - NOT OK      
 |        
 |         
 |         
 ├── Company002
 |       (empty)
 ├── Company003
 |       (empty)
 └── Company004
         (empty)     

There will be probably needed update IdM behavior with unique codes of role catalogue IDK or something else? :(. Try thing about it.

Affected version: probably all


Related issues

Related to extras - Task #1753: Upgrade wf for synchronization of groups from LdapClosedPatrik Stloukal07/16/2019

Actions
Actions #1

Updated by Patrik Stloukal about 5 years ago

  • Related to Task #1753: Upgrade wf for synchronization of groups from Ldap added
Actions #2

Updated by Patrik Stloukal about 5 years ago

  • Status changed from New to In Progress

this ticket is getting fixed in #1753

Actions #3

Updated by Ondřej Kopr about 5 years ago

  • Project changed from IdStory Identity Manager to extras
  • Category deleted (Workflow)
  • Status changed from In Progress to Needs feedback
  • Target version set to 1.4.0
  • % Done changed from 0 to 100

Review was done by me in ticket: #1753.

Actions #4

Updated by Patrik Stloukal about 5 years ago

  • Status changed from Needs feedback to Resolved

merged to extras develop

Actions #5

Updated by Patrik Stloukal about 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF