Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 28 Next »


Activities



CAUTION:

If there is a limitation on the number of connections to the domain controller and an Approval activity is desired in the same workflow as processing a large number of operations, it is recommended to separate edirectory activities within a workflow/ snippet separate from the workflow in which the Approval activity  is used (because approval has a default persistence mechanism). In that way, the workflow/ snippet will not have operations/ activities persisted and the workflow will run normally without the persistency flag. Only the workflow with Approval activity will be persisted.


Connect to eDirectory

This activity connects to eDirectory.The Output of this activity should be used as input for all Connection parameters used for activities placed under eDirectory category.

Activity Parameters

The Connect to eDirectory activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Ldap Host (text box editor type) (type: string): the eDirectory Ldap Host. Can be inserted the Novell server IP or Name (in the screenshot above can be seen the IP: 10.201.0.27).
  • Ldap Port (text box editor type) (type: Int32): the eDirectory port, in this case the LDAP assigned port (389).
  • Login DN (text box editor type) (type: string): the DN (Distinguished Name) of the user which will connect to Novell (e.g. cn=Admin, ou=Administrators,o=users, where Admin is the username).
  • Password (password editor type) (type: string): the password for the provided username.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the connection. (This parameter is used only when the user wants to send an encrypted password from outside the workflow, for example Flowster Studio Portal).

The Read Only Output variable are the possible output values that the activity will provide:

  • Connection (type: object): outputs an eDirectory Connection. This parameter should be used as input for all Connection parameters used for activities placed under eDirectory category.
 

As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.

Execution: the activity will try to established a connection to the given Novell server. If succeeded, True will be outputted:







Disconnect from eDirectory

This activity disconnects from eDirectory.

Activity Parameters

The Disconnect from eDirectory activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Connection (text box editor type) (type: object): the eDirectory Connection. The output parameter from Connect To eDirectory activity should be used as Input here.





Add User To Group

This activity adds a computer to specified group.

Activity Parameters

The Add User to Group activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • group DN (text box editor type) (type: string):  the DN String value for the group where the user will be added. For example, "CN=FlowsterGroup,o=FlowsterDemo", where FlowsterGroup is the name for the group and FlowsterDemo is the parent container of the group).
  • user DN (text box editor type) (type: string): the DN String value for the user which will be added to the group. For example, "CN=FlowsterUser,o=FlowsterDemo", where FlowsterUser is the name of the user and FlowsterDemo is the parent container of the user).

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: boolean): outputs the status of the operation: True is successful, otherwise False.
 

As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.

Execution: the activity will check for the given DNs (Group and User DN) and if both found, it will add the user to the group:


The membership can be seen on the Group, for example, in the Members tab (NetIQ iManager was used for browsing purposes):







 

Change User Password

This activity changes the password of a user account.

Activity Parameters

The Change User Password activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • userDN (text box editor type) (type: string): the DN String value for the user which will be have the password changed. For example, "CN=FlowsterUser,o=FlowsterDemo", where FlowsterUser is the name of the user and FlowsterDemo is the parent container of the user).
  • Password (password editor type) (type: string): the new password for the provided username.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password. (This parameter is used only when the user wants to send an encrypted password from outside the workflow, for example Flowster Studio Portal).

Execution: the activity will modify the user's password with the new given value:







Create Computer

This activity creates a new entry of class 'Computer' in eDirectory.

Activity Parameters

The Create Computer activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • CN String (text box editor type) (type: string): the CN String value for the new computer. The format should be "ComputerName" (for example, "FlowsterComputer", where FlowsterComputer is the name for the new machine).
  • Container DN (text box editor type) (type: string): the parent container for the new created computer. For example, "o=FlowsterDemo", where FlowsterDemo will be the parent container of the new machine.

The Read Only Output variable are the possible output values that the activity will provide:

  • Entry DN (type: string): outputs the DN of the new created computer.
 

As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.

Execution: the activity will check for the given Container (Container DN) and if found, it will create a new computer with the provided name (CN String):


The newly created machine can be seen under the given parent container (NetIQ iManager was used for browsing purposes):







Create Group

This activity creates a new entry of class 'Group' in eDirectory.

Activity Parameters

The Create Group activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • CN String (text box editor type) (type: string): the CN String value for the new group. The format should be "GroupName" (for example, "FlowsterGroup", where FlowsterGroup is the name for the new group).
  • Container DN (text box editor type) (type: string): the parent container for the new created group. For example, "o=FlowsterDemo", where FlowsterDemo will be the parent container of the new group.

The Read Only Output variable are the possible output values that the activity will provide:

  • Entry DN (type: string): outputs the DN of the new created group.
 

As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.

Execution: the activity will check for the given Container (Container DN) and if found, it will create a new group with the provided name (CN String):


The newly created group can be seen under the given parent container (NetIQ iManager was used for browsing purposes):







 

Create User

This activity creates a new entry of class 'User' in eDirectory.

Activity Parameters

The Create User activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • CN String (text box editor type) (type: string): the CN String value for the new user. The format should be "UserName" (for example, "FlowsterUser", where FlowsterUser is the name for the new user).
  • Container DN (text box editor type) (type: string): the parent container for the new created user. For example, "o=FlowsterDemo", where FlowsterDemo will be the parent container of the new user.
  • Given Name (text box editor type) (type: string): the first name of the new created user.
  • Mail (text box editor type) (type: string): the mail attribute of the new created user.
  • Password (text box editor type) (type: string): the password for the User.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the User. (This parameter is used only when the user wants to send an encripted password from outside the workflow, for example Flowster Portal)
  • sn (text box editor type) (type: string): the last name of the new created user.
  • Telephone number (text box editor type) (type: string): the telephone number attribute for the new created user.

The Read Only Output variable are the possible output values that the activity will provide:

  • Entry DN (type: string): outputs the DN of the new created user.
 

As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.

Execution: the activity will check for the given Container (Container DN) and if found, it will create a new user with the provided name (CN String) and attributes (Given Name, SN, Mail, Telephone Number):


The newly created group can be seen under the given parent container (NetIQ iManager was used for browsing purposes):







Delete Entry

This activity deletes specified entry from eDirectory.

Activity Parameters

The Delete Entry activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Entry DN (text box editor type) (type: string): the DN String value for the object to be deleted. For example, "CN=FlowsterUser,o=FlowsterDemo", where FlowsterUser is the name of the user and FlowsterDemo is the parent container of the user.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: boolean): outputs the status of the operation.

Execution: depending on the given input object (Entry DN - user, computer or group), the activity will delete the entry from the specified Novell server:








Edit Entry

This activity edits specified attribute(s) values of a specified input entry.

Activity Parameters

The Edit Entry activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Attributes (collection editor type) (type: string): the attributes as a collection for the eDirectory entry that you want to edit. In our example the activity will edit the SN and the Mail attributes. For the Name column insert the exact name of the attribute and for the Value column insert the new value.
  • CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "SN,FlowsterNewSN;Mail,demoNew@fmrp.intern".
  • Entry DN (text box editor type) (type: string): the DN String value for the user which will the attributes edited. For example, "CN=FlowsterUser,o=FlowsterDemo", where FlowsterUser is the name of the user and FlowsterDemo is the parent container of the user).
 

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables.

Execution: the activity will edit the specified attributes for the given entry (in our example, for an user):







 

Remove User from Group

This activity removes specified user from specified group.

Activity Parameters

The Remove User from Group activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • group DN (text box editor type) (type: string):  the DN String value for the group where the user will be removed from. For example, "CN=FlowsterGroup,o=FlowsterDemo", where FlowsterGroup is the name for the group and FlowsterDemo is the parent container of the group).
  • user DN (text box editor type) (type: string): the DN String value for the user which will be removed from the group. For example, "CN=FlowsterUser,o=FlowsterDemo", where FlowsterUser is the name of the user and FlowsterDemo is the parent container of the user).

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: boolean): outputs the status of the operation: True is successful, otherwise False.
 

As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.

Execution: the activity will check for the given DNs (Group and User DN) and if both found, it will remove the user from the group:








List Entries

This activity returns all the entries in the specified container. No attributes are returned.

Activity Parameters

The List Entries activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Search Base (text box editor type) (type: string): the container DN where the search is done. For example, "o=FlowsterDemo", meaning that the activity will search in this specific container after its entries.
  • Search Filter (text box editor type) (type: string): the search filter. If left empty, the activity will return all objects from the given container (Search Base). There can be also used the following filters:
    • ObjectClass=User: will return only the entries of type User
    • ObjectClass=Group: will return only entries of type Group
    • ObjectClass=Computer: will return only entries of type Computer
    • combinations of the above mentioned filters

The Read Only Output variable are the possible output values that the activity will provide:

  • DN List (type: List<string>): outputs a list of strings containing the found DN for each object that matches the filter.
 

As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.

Execution: the activity will search for entries in the given container, depending on the provided filter (if the filter is empty, all entries will be listed):






Search Attributes

This activity searches for attribute values based on the search filter of the first matching DN.

Activity Parameters

The Search Attributes activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Search Base (text box editor type) (type: string): the container DN where the search is done. For example, "o=FlowsterDemo", meaning that the activity will search in this specific container after its entries.
  • Search Filter (text box editor type) (type: string): the search filter:
    • If left empty: the activity will return the container's attributes. It will also be left empty is a CN is provided at the Search Base field
    • ObjectClass=User: will return only the attributes for the entries of type User
    • ObjectClass=Group: will return only the attributes for the entries of type Group
    • ObjectClass=Computer: will return only the attributes for the entries of type Computer
    • combinations of the above mentioned filters (except empty)

The Read Only Output variable are the possible output values that the activity will provide:

  • Attributes List (type: List<KeyValuePair<string,string>>): outputs a list of KeyValuePair string containing the found attribute name and value for the first object that matches the filter.  
  • Attributes List Array (type: List<KeyValuePair<string,string[]>>): outputs a list of KeyValuePair string, string[] containing the found attribute name and all the values for the first object that matches the filter.
 

As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.

Execution: depending on the given Search Base and Search Filters, the activity will output a list with all found attributes. Below there are some examples of using the activity with different search filters and search bases:

  • Search Base is a container, no filter provided:
    • activitycontent:
    • activity execution:


  • Search Base is a container, filter for Users provided:
    • activity content:
    • activity execution:


  • Search Base is a container, filter for Groups provided:
    • activity content:
    • activity execution:


  • Search Base is an User, no filter provided
    • activity content:
    • activity execution:


  • Search Base is a Group, no filter provided:
    • activity content:
    • activity execution:


  • Search Base is a Computer, no filter provided:
    • activity content:
    • activity execution:


If an attribute has multiple values, use the output parameter Attributes List Array to extract all the values from the attribute. E.g attribute = objectClass with multiple values like 'top;organizationalUnit'. In order to extract all values from the objectClass attribute, not just the first one, use a ForEach activity to iterate through the string[] returned by Attributes List Array parameter:

Rename Entry

This activity renames the cn attribute for an entry in Novell eDirectory.

Activity Parameters

The Rename Entry activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • New DN (text box editor type) (type: string): the new CN string value.
  • Old DN (text box editor type) (type: string): the old DN String value for the user which will be renamed. For example, "CN=FlowsterUser,o=FlowsterDemo", where FlowsterUser is the name for the userand FlowsterDemo is the parent container of the user).
  • Parent DN (text box editor type) (type: string): the parent DN of the entry. For example, "o=FlowsterDemo".

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: string) outputs the status of the operation. 
 

Execution: the activity will search the user in the given container and after the given DN (Old DN). If found, it will renamed the user according to the new name (New DN):


The renamed can be seen under the given parent container (NetIQ iManager was used for browsing purposes):



  • No labels