New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Allows WordPress to authenticate, authorize, create and update users against Active Directory | You have to log in to add a translation. | Details |
Original untranslated
Allows WordPress to authenticate, authorize, create and update users against Active Directory
You have to log in to edit this translation. |
|||
| ↑ | Active Directory Integration | You have to log in to add a translation. | Details |
Original untranslated |
|||
| For existing ADI 1 users, who won't upgrade to <em>Next ADI</em>: | You have to log in to add a translation. | Details | |
Original untranslated
For existing ADI 1 users, who won't upgrade to <em>Next ADI</em>:
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Good news, everyone! We rewrote this plugin from scratch and added new features and a smoother user interface. Please welcome <a href="https://wordpress.org/plugins/next-active-directory-integration">Next ADI</a>!↵ The new <em>Next ADI</em> plugin will always stay free and open source. The development can be tracked on <a href="https://github.com/NeosIT/active-directory-integration2">GitHub</a>. Along with <em>Next ADI</em> we also intruduce our <a href="https://www.active-directory-wp.com">professional support</a> for agencys, developers and site owners. Please note that the ADI v1 plugin is now deprecated and will not longer be supported. | You have to log in to add a translation. | Details | |
Original untranslated
Good news, everyone! We rewrote this plugin from scratch and added new features and a smoother user interface. Please welcome <a href="https://wordpress.org/plugins/next-active-directory-integration">Next ADI</a>!↵
The new <em>Next ADI</em> plugin will always stay free and open source. The development can be tracked on <a href="https://github.com/NeosIT/active-directory-integration2">GitHub</a>. Along with <em>Next ADI</em> we also intruduce our <a href="https://www.active-directory-wp.com">professional support</a> for agencys, developers and site owners. Please note that the ADI v1 plugin is now deprecated and will not longer be supported.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| A common mistake is that the Base DN is set to a wrong value. If the user resides in an Organizational Unit (OU) that is not "below" the Base DN the groups the user belongs to can not be determined. A quick solution is to set the Base DN to something like <code>dc=mydomain,dc=local</code> without any OU.↵ Another common mistake is to use <code>ou=users,dc=mydomain,dc=local</code> instead of <code>cn=users,dc=mydomain,dc=local</code> as Base DN. Do you see the difference? I recommend to use tools like <a href="http://technet.microsoft.com/en-us/library/cc773354(WS.10).aspx">ADSIedit</a> to learn more about your Active Directory. | You have to log in to add a translation. | Details | |
Original untranslated
A common mistake is that the Base DN is set to a wrong value. If the user resides in an Organizational Unit (OU) that is not "below" the Base DN the groups the user belongs to can not be determined. A quick solution is to set the Base DN to something like <code>dc=mydomain,dc=local</code> without any OU.↵
Another common mistake is to use <code>ou=users,dc=mydomain,dc=local</code> instead of <code>cn=users,dc=mydomain,dc=local</code> as Base DN. Do you see the difference? I recommend to use tools like <a href="http://technet.microsoft.com/en-us/library/cc773354(WS.10).aspx">ADSIedit</a> to learn more about your Active Directory.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, this works. But you have to add the line <code>TLS_REQCERT never</code> to your ldap.conf on your web server.↵ If yout don't already have one create it. On Windows systems the path should be <code>c:\openldap\sysconf\ldap.conf</code>.↵ Another and even simpler way is to add LDAPTLS_REQCERT=never to your environment settings. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, this works. But you have to add the line <code>TLS_REQCERT never</code> to your ldap.conf on your web server.↵
If yout don't already have one create it. On Windows systems the path should be <code>c:\openldap\sysconf\ldap.conf</code>.↵
Another and even simpler way is to add LDAPTLS_REQCERT=never to your environment settings.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| It is never a good idea to allow special characters in usernames! For ADI it won't be a problem, but in Wordpress only lowercase letters (a-z) and numbers are allowed. The only option is to change the usernames in AD. Hey! Stop! Don't shoot the messenger. | You have to log in to add a translation. | Details | |
Original untranslated
It is never a good idea to allow special characters in usernames! For ADI it won't be a problem, but in Wordpress only lowercase letters (a-z) and numbers are allowed. The only option is to change the usernames in AD. Hey! Stop! Don't shoot the messenger.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Here we have a special problem with the builtin security group "Domain Users". In detail: the security group "Domain Users" is usually the primary group of all users. In this case the members of this security group are not listed in the members attribute of the group. To import all users of the security group "Domain Users" you must set the option "Import members of security groups" to "<strong>Domain Users;id:513</strong>". The part "id:513" means "Import all users whos primaryGroupID is 513." And as you might have guessed, 513 is the ID of the security group "Domain Users". | You have to log in to add a translation. | Details | |
Original untranslated
Here we have a special problem with the builtin security group "Domain Users". In detail: the security group "Domain Users" is usually the primary group of all users. In this case the members of this security group are not listed in the members attribute of the group. To import all users of the security group "Domain Users" you must set the option "Import members of security groups" to "<strong>Domain Users;id:513</strong>". The part "id:513" means "Import all users whos primaryGroupID is 513." And as you might have guessed, 513 is the ID of the security group "Domain Users".
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Not all attribute types from the Active Directory schema are supported and there are some special types. Types marked as SyncBack can be synced back to AD (if the attribute is writeable). | You have to log in to add a translation. | Details | |
Original untranslated
Not all attribute types from the Active Directory schema are supported and there are some special types. Types marked as SyncBack can be synced back to AD (if the attribute is writeable).
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| You must give your users the permission to change their own attributes in Active Directory. To do so, you must give write permission on "SELF" (internal security principal). Run ADSIedit.msc, right click the OU or CN all your users belong to, choose "Properties", go on tab "Security", add the user "SELF" and give him the permission to write. | You have to log in to add a translation. | Details | |
Original untranslated
You must give your users the permission to change their own attributes in Active Directory. To do so, you must give write permission on "SELF" (internal security principal). Run ADSIedit.msc, right click the OU or CN all your users belong to, choose "Properties", go on tab "Security", add the user "SELF" and give him the permission to write.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Use the <a href="http://bt.steindorff.de/">bug tracker</a> (see above) at http://bt.steindorff.de/. | You have to log in to add a translation. | Details | |
Original untranslated
Use the <a href="http://bt.steindorff.de/">bug tracker</a> (see above) at http://bt.steindorff.de/.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. You'll find the bug tracker at http://bt.steindorff.de/. You can report issues anonymously but it is recommended to create an account. This is also the right place for feature requests. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. You'll find the bug tracker at http://bt.steindorff.de/. You can report issues anonymously but it is recommended to create an account. This is also the right place for feature requests.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If you activate "Automatic User Creation" and "Automatic User Update" you may store any AD attribute to the table wp_usermeta. You can set the meta key as you like or use the default behavior, where the meta key is set to <code>adi_<attribute></code> (e.g. <code>adi_physicaldeliveryofficename</code> for the Office attribute). You can find a list of common attributes on the "User Meta" tab. | You have to log in to add a translation. | Details | |
Original untranslated
If you activate "Automatic User Creation" and "Automatic User Update" you may store any AD attribute to the table wp_usermeta. You can set the meta key as you like or use the default behavior, where the meta key is set to <code>adi_<attribute></code> (e.g. <code>adi_physicaldeliveryofficename</code> for the Office attribute). You can find a list of common attributes on the "User Meta" tab.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. Since 1.0-RC1 you get more informations from the Test Tool by setting WordPress into debug mode. Simply add DEFINE('WP_DEBUG',true); to your wp-config.php. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Since 1.0-RC1 you get more informations from the Test Tool by setting WordPress into debug mode. Simply add DEFINE('WP_DEBUG',true); to your wp-config.php.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, you can. Just put "ldaps://" in front of the server in the option labeled "Domain Controller" (e.g. "ldaps://dc.domain.tld"), enter 636 as port and deactivate the option "Use TLS". But have in mind, that | You have to log in to add a translation. | Details | |
Original untranslated
Yes, you can. Just put "ldaps://" in front of the server in the option labeled "Domain Controller" (e.g. "ldaps://dc.domain.tld"), enter 636 as port and deactivate the option "Use TLS". But have in mind, that
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.