What is the Authentication error #1000?

The authentication error #1000 is displayed if an action with the MDU was not authorized.

• The MDU action was not confirmed within a certain time window using a privileged key on the terminal.
• The key used for authorization is not authorised to operate the MDU.
• The key used for authorization does not have locking authorisation for the door or is no longer valid.
• The configuration of the terminal is faulty so that valid keys are no longer recognized.
• The terminal's reader is malfunctioning and can no longer read keys.

Make sure that you follow the correct sequence of steps when executing MDU actions. Almost all actions with the MDU require authorization using a privileged key (dual control principle). This is to prevent unauthorized persons from manipulating the terminals using the MDU.

Follow these steps:

1. Select the desired action on the MDU and approach the terminal.
2. The terminal starts to flash and expects authorization - “Authorize at terminal” appears on the MDU
3. Remove the MDU from the terminal
4. Hold the privileged key against the terminal - The LED should flash positive (white, green or blue) and beep once.
5. Remove the key from the terminal
6. Hold the MDU against the terminal again - Data transfer now continues.
7. (Depending on the action selected) - Wait until the transfer is complete or for further prompts on the MDU.

The privileged key must fulfill the following criteria:

1. It always requires locking authorization for the access point in question. (it makes sense to select keys with general locking authorization as privileged keys)
2. The key must be valid (check the start and end of validity - ideally unlimited)
3. The key requires the two special privileges “Parameterization privilege (MDU)” and “MDU audit trail privilege”

You can check these properties in the DG2 software under “Profiles” > “ Persons”. Select the relevant person from the list. If one or more of the criteria are not met, change the relevant settings and save them. Then issue the key again. It should now be accepted as a privileged key.

Use the MDU to read the terminal info and check whether the name of the terminal and the time are correct. If they are inaccurate, this could be the cause of authorization error #1000.

A reset of the terminal or access via code usually helps here. The terminal can then be reprogrammed.

If all other causes have been ruled out, the installation of the terminal should be checked.

A terminal component could be damaged or not connected correctly. Therefore, check that everything is well connected and that no external damage is visible.

If the error persists after checking the installation, the reader or logic module may be defective and should be replaced.