AnsweredAssumed Answered

Active Directory Transfer Use-Case

Question asked by Rajkiran Paul on Nov 21, 2016
Latest reply on Dec 7, 2016 by Vijayabaskar Balakrishnan

Like • Show 0 Likes0
Comment • 6

Hi All,

The below is the use case which we want to implement:

1)We have an attribute named "OU" in user repository.Based on this "OU" value ,user is getting provisioned in respective OU of Active Directory.

When user's OU attribute will change from User repository,user should change from one OU to another OU of Active Directory.

Please suggest how to achieve this .

Boris Lekumovich

Nov 21, 2016 5:47 PM

Correct Answer

Consider the following approach:

Create a "dummy" application
- Create a local entitlement collector
- Create a local entitlement
Create a fulfillment workflow with a provisioning node to move account to a specified OU
- Assign the fulfillment workflow to the application
Create a rule type Attribute change
- In the Actions section, choose the local entitlement which you created

When an OU attribute change will be detected, a workflow will be triggered (to add the local entitlement) which will move the account to a new OU.

Obviously you will have to feed the provisioning node with the correct information such as:

DN of the account
The new location of the account

See the reply in context

No one else had this question

Outcomes

Amit Khatua Nov 21, 2016 8:52 AM

Active Directory build-in connector Move Account capability can be used to achieve this.

Account Name - Existing distinguishedName

New Parent DN - New distinguishedName (the one which is getting generated according to your business logic)

Hope that helps

Actions

Rajkiran Paul @ Amit Khatua on Nov 21, 2016 9:09 AM

Thank you.But how to automate this?How to trigger it using a rule.

Actions

Boris Lekumovich

@ Rajkiran Paul on Nov 21, 2016 5:47 PM

Consider the following approach:

Create a "dummy" application
- Create a local entitlement collector
- Create a local entitlement
Create a fulfillment workflow with a provisioning node to move account to a specified OU
- Assign the fulfillment workflow to the application
Create a rule type Attribute change
- In the Actions section, choose the local entitlement which you created

When an OU attribute change will be detected, a workflow will be triggered (to add the local entitlement) which will move the account to a new OU.

Obviously you will have to feed the provisioning node with the correct information such as:

DN of the account
The new location of the account

Actions

Rajkiran Paul @ Boris Lekumovich on Dec 5, 2016 6:36 AM

Hi Boris,

We have created the fulfilment workflow. But it seems its not triggering.Please help us to create a fulfilment workflow.

Actions

Boris Lekumovich

@ Rajkiran Paul on Dec 6, 2016 11:02 PM

I don't have a full visibility on what you did and how it was configured.

Hard to assist when the information is not sufficient.

Actions

Vijayabaskar Balakrishnan

@ Rajkiran Paul on Dec 7, 2016 1:22 AM

Hope you must be mapping the attribute OU in any of the Aveksa Attributes, so you can use attribute rule type having the condition on mapped attribute.

Definitely you can trigger the workflow with some dummy action.

Actions

6 Replies

Amit Khatua Nov 21, 2016 8:52 AM
Mark Correct
Correct Answer
Active Directory build-in connector Move Account capability can be used to achieve this.
Account Name - Existing distinguishedName
New Parent DN - New distinguishedName (the one which is getting generated according to your business logic)

Hope that helps
Like • Show 0 Likes0
Actions
- Rajkiran Paul @ Amit Khatua on Nov 21, 2016 9:09 AM
  Mark Correct
  Correct Answer
  Thank you.But how to automate this?How to trigger it using a rule.
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ Rajkiran Paul on Nov 21, 2016 5:47 PM
    Unmark Correct
    Correct Answer
    Consider the following approach:
    Create a "dummy" application
    Create a local entitlement collector
    Create a local entitlement
    Create a fulfillment workflow with a provisioning node to move account to a specified OU
    Assign the fulfillment workflow to the application
    Create a rule type Attribute change
    In the Actions section, choose the local entitlement which you created
    
    When an OU attribute change will be detected, a workflow will be triggered (to add the local entitlement) which will move the account to a new OU.
    
    Obviously you will have to feed the provisioning node with the correct information such as:
    DN of the account
    The new location of the account
    Like • Show 0 Likes0
    Actions
    - Rajkiran Paul @ Boris Lekumovich on Dec 5, 2016 6:36 AM
      Mark Correct
      Correct Answer
      Hi Boris,
      
      We have created the fulfilment workflow. But it seems its not triggering.Please help us to create a fulfilment workflow.
      
      Like • Show 0 Likes0
      Actions
      - Boris Lekumovich @ Rajkiran Paul on Dec 6, 2016 11:02 PM
        Mark Correct
        Correct Answer
        I don't have a full visibility on what you did and how it was configured.
        Hard to assist when the information is not sufficient.
        Like • Show 0 Likes0
        Actions
  - Vijayabaskar Balakrishnan @ Rajkiran Paul on Dec 7, 2016 1:22 AM
    Mark Correct
    Correct Answer
    Hope you must be mapping the attribute OU in any of the Aveksa Attributes, so you can use attribute rule type having the condition on mapped attribute.
    
    Definitely you can trigger the workflow with some dummy action.
    Like • Show 0 Likes0
    Actions