This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
en:software:tim:timer:createusersfromldapgroup [2014/12/01 14:19] duc.le created |
en:software:tim:timer:createusersfromldapgroup [2021/07/01 09:52] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)// | ||
- | |||
=======createUsersFromLdapGroup======== | =======createUsersFromLdapGroup======== | ||
==== Description ==== | ==== Description ==== | ||
- | This timer gets all members from a LDAP group and places them in T!M - Task !n Motion. It also assigns the given rights to the users found. | + | This timer gets all members from a LDAP group and places them in TIM. It also assigns the given rights to the users found. |
==== Webservice Name ==== | ==== Webservice Name ==== | ||
Line 9: | Line 7: | ||
==== Webservice Methode ==== | ==== Webservice Methode ==== | ||
- | createUsersFromLdapGroup | + | <code>createUsersFromLdapGroup</code> |
- | ---- | + | |
==== Parameter ==== | ==== Parameter ==== | ||
== DN-path from the LDAP == | == DN-path from the LDAP == | ||
Line 16: | Line 14: | ||
- | \\ == Rights in T!M == | + | \\ == Rights in TIM == |
Here, the rights can be given that the timer automatically assigns to the given group. If more than one per group rights are given, they must be separated with a comma(",").The following values are possible: | Here, the rights can be given that the timer automatically assigns to the given group. If more than one per group rights are given, they must be separated with a comma(",").The following values are possible: | ||
Line 34: | Line 32: | ||
If the group is too large to synchronize all users in a single pass, you can be specified using the offset, from which user number of the sync should be started. (see [[#Example]]) | If the group is too large to synchronize all users in a single pass, you can be specified using the offset, from which user number of the sync should be started. (see [[#Example]]) | ||
---- | ---- | ||
- | |||
==== Example ==== | ==== Example ==== | ||
<code properties retrieves 100 User from the DN and gives these users processmanage and member rights> | <code properties retrieves 100 User from the DN and gives these users processmanage and member rights> | ||
Line 50: | Line 47: | ||
<code properties> "CN=TIM-Prozessmanager,OU=LDAP-Wiki,DC=tim,DC=local","member,processmanager","100","0" </code> | <code properties> "CN=TIM-Prozessmanager,OU=LDAP-Wiki,DC=tim,DC=local","member,processmanager","100","0" </code> | ||
- | {{en:software:tim:timer:ldaptimer.png?500 |}} \\ | + | {{en:software:tim:timer:timerIdentityManager_en.png |}} \\ |
{{:software:tim:timer:ldap-log.jpg?700 |}} \\ | {{:software:tim:timer:ldap-log.jpg?700 |}} \\ | ||
- | {{en:software:tim:timer:ldap_result.png?400 |}} \\ | + | {{:software:tim:timer:timerIdentityManager2_en.png |}} \\ |
---- | ---- | ||
- | {{ ec:software:tim:timer:ldap_result2.png?200|}} | ||
After this, a second timer is created, which has the following parameters: | After this, a second timer is created, which has the following parameters: | ||
<code properties> | <code properties> | ||
Line 61: | Line 57: | ||
</code> | </code> | ||
In the group **TIM-Admin** our User "User1" is registered again, that passes through after the Timer looks like this: | In the group **TIM-Admin** our User "User1" is registered again, that passes through after the Timer looks like this: | ||
+ | {{ :software:tim:timer:timerIdentityManager3_en.png|}} |