You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have LDAP Auth and struct working well. I can add a field type of User to my forms and clicking in them and starting to type allows me to select from a list of users.
I needed to add chained auth plugin (http://www.dokuwiki.org/plugin:authchained) to allow a local script on the server to schedule exports of certain pages. The set up of this process went well and I was able to use a local account for this export and continue to login using LDAP for the other users.
However since I installed the chained auth plugin the struct user fields no longer show suggestions for user names unless those names are the local accounts. When I disable the chained auth plugin normal lookup service was restored.
It appears that the chained part of the user lookup doesn't work with Struct or struct doesn't work with chained.
Has anyone else had this issue or found a fix?
The text was updated successfully, but these errors were encountered:
I have LDAP Auth and struct working well. I can add a field type of User to my forms and clicking in them and starting to type allows me to select from a list of users.
I needed to add chained auth plugin (http://www.dokuwiki.org/plugin:authchained) to allow a local script on the server to schedule exports of certain pages. The set up of this process went well and I was able to use a local account for this export and continue to login using LDAP for the other users.
However since I installed the chained auth plugin the struct user fields no longer show suggestions for user names unless those names are the local accounts. When I disable the chained auth plugin normal lookup service was restored.
It appears that the chained part of the user lookup doesn't work with Struct or struct doesn't work with chained.
Has anyone else had this issue or found a fix?
The text was updated successfully, but these errors were encountered: