Find user plugin

This plugin allows unauthenticated users to search for an user account to impersonate. This may be useful to randomly provide an identifier depending on allowed searching attributes and excluded values.


FindUser plugin works only if Impersonation plugin is enabled.


Just enable it in the Manager (section “plugins”). Then, set searching attributes used for selecting accounts and to randomly suggest one of them in login form. Excluding attributes can also be defined to exclude some user accounts and avoid to provide them.

  • Parameters:

    • Activation: Enable / Disable this plugin

    • Character used as wildcard: Character that can be used by users as wildcard. An empty value disable wildcarded search requests

    • Parameters control: Regular expression used for checking searching values syntax

    • User accounts URL: User database URL to search on if REST backend is used. Let it blank to use default user data URL.

    • Searching attributes: For each attribute, you have to set a key (attribute as defined in UserBD) and a value that will be displayed in login form as placeholder. Values can be a multivalued list separated by multiValuesSeparator parameter (General Parameters > Advanced parameters > Separator). Attibutes can be sorted by adding a X_ before their name where X is a number. See note below.

    • Excluding attributes: You can defined here attributes used for excluding accounts. Set keys corresponding to UserBD attributes and values to exclude. Values can be a multivalued list separated by multiValuesSeparator parameter


By default, simple searching attributes are mandatory to restrict the number of returned entries. To set an attribute as optional, you can use the following syntax:

uid##1  =>  UID


You can provide a ‘multiValuesSeparator’ separated list of allowed searching values that will be displayed as an HTML <select> list

format = attribute#placeholder[#empty] -> value1; placeholder1; value2; placeholder2

For example

format = uid#Identity     like `dwho; Dr Who; rtyler; Rose Tyler; msmith; Mr Smith`

format = uid#Identity#1   like `dwho; Dr Who; rtyler; Rose Tyler (allow empty value)`

format = 1_uid#Identity#1 like `2_dwho; Dr Who; 1_rtyler; Rose Tyler; dalek; Dalek`
(Attributes will be sorted by number, those without number will be appended at the end of the list)


Searching request is built based on provided parameters value depending on users backend like this:

request => searchAttr1=value && searchAttr2=value && not excludeAttr1=value && not excludeAttr2=value


In some cases (like Choice authentication with SSL and Ajax), FindUser Ajax request can be blocked by Content Security Policy.

You may have to allow <Portal>/finduser in CSP General Parameters > Advanced Parameters > Security > Content security policy


This plugin works only with a users backend and of course if the searching or excluding attributes are existing.


With AuthChoice, you must set which module will be called by this plugin (Backend choice by users).