FatSquirrel

Hey @quantum_leap
this is the first time we have heard about this issue.
The only time we display an overlay blocking user interaction is during the time we fetch the settings from the admin-ajax.php.

Can you please check the developer tools (default key F12) and see if any error messages appear inside the console tab?

Which version of Firefox are you currently using?

Hey @mlipenk
we have added a fix for this issue and it will be released as part of the 2.1.8 update.
Thank you very much for contributing to the plugin.

Hey @russ668,
can you please provide us with some detail on how your multisites are configured?

Are you using subdomains for the individual sites or are you using subdirectories?

Hey @canadabri
I′m looking into the issue you have reported and my colleague has send me your log file.

First off, the test-authentication does have a bug preventing the authorization groups from being registered correctly. This means all users will be authenticated even if the authorization groups should prevent him from doing so. This only happens during the test-authentication and we have already implemented a fix (internal issue tracker #ADI-665). This fix will be released in the upcoming 2.1.6 update.

I′ll be checking your logs and try to replicate the issue.

Hey @shmew22 and @canadabri
we have just release a new version (2.1.5). This release contains a fix for the authorization group issue you have reported.
Please update your plugin and check if the issue has been resolved.

Thank you for letting us know about this issue!

Hey @5tu
we have just released a new version (2.1.5). Part of the new release is a fix for the issue you have reported.

Thank you again for reporting this bug.

We do not have a fixed date, but we will try to push the next release as soon as possible (due to the deprecation of mcrypt).

My guess would be the end of next week, but don′t quote me on that ??

I will let you know, when the next release is published.

Hey aleksluik

we are aware of the upcoming removal of mcrypt. We have already implemented an alternative solution, using https://github.com/defuse/php-encryption .

We will be releasing these changes in the next version of NADI.

Hey mzemann,

thanks for reporting your issue.

I have just checked the problem you are describing. Currently you are able to enter a custom description for any attributes you want to show inside the users profile. But that description is never used. This is not the intended behavior.

I will create a ticket in our internal issue tracker.

This is what it should be like:

Is there a custom description for the attribute?
If yes, display that description as the name.
If no, use the default name from the Active Directory.

If I fix the issue, I will let you know.

Hey genelynancheta

have you successfully configured your plugin and connected to your Active Directory?
You should have a valid Domain SID inside your Configuration –> Environment tab

Hey ikkarus13

once a user has been removed from your Active Directory and you trigger a synchronization, that user will be disabled in your WordPress installation.

It will still show the user in your Users list, but he will be disabled and it should display a message: User no longer exists in Active Directory.

If you could provide any log output, that would be greatly appreciated.

Hey taragnolini

We only support one Active Directory domain.

Ok, I′m very glad to hear.

Sorry if we might have misunderstood each other.

If you encounter any further problems, please let us know.

Hey

Try the following:
You have a user in your WordPress Users list: someuser
You can login using [email protected] and the password
You only want to login using someuser and the password

Go into your NADI configuration –> User –> Account suffix and enter your company.com value

You will now be able to login using only someuser and the password

Sorry if we might have misunderstood your issue, but this is what you need to do, in order to login.

I hope this resolves your issue.

Hey Slenzi,

we only support login using the email. There is no implementation for login using the sAMAccountname.

In most cases, the sAMAccountname plus suffix is equal to the email.

You could use single sign on. For further information please have a look at our official documentation.