Debian + Error during installation

Can I reconfigure the timewindow to 60 for all in the db or do I have to create new tokens/re-enroll them?

It works fine! :slight_smile:
My last question :smiley:

Is there a self service for the users so that the user can enroll his token
by himself and create the QR code?On Monday, March 2, 2015 at 10:49:24 PM UTC+1, Cornelius Kölbel wrote:

yes, fixes this, too.
Good night.
Am 02.03.2015 um 22:32 schrieb Stefan Steuer:

I’ll try it in the Morning :wink:
Should that File also fix the Problem while Creating a Token for a User
with “umlaut”?

What does the audit say?

I guess this the OTP value is wrong.
It is TOTP, isnt it?

Maybe the timewindow is a bit narrow.
What values do you have there?

Kind regards
CorneliusAm 03.03.2015 um 19:12 schrieb Stefan Steuer:

Dear Cornelius,
I don’t know why but when I type in my username and the OTP from
google auth sometimes the login is successful - sometimes unsucessful.
Do you have any idea?!

You received this message because you are subscribed to the Google
Groups “privacyidea” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to privacyidea+unsubscribe@googlegroups.com
mailto:privacyidea+unsubscribe@googlegroups.com.
To post to this group, send email to privacyidea@googlegroups.com
mailto:privacyidea@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/privacyidea/d63e09cb-e1b4-4e47-9348-8f067a8ac29b%40googlegroups.com
https://groups.google.com/d/msgid/privacyidea/d63e09cb-e1b4-4e47-9348-8f067a8ac29b%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.

I’m so gooood :slight_smile:

I just found the error. The QR should not has the parameter "&counter=0"
unsafe:otpauth://hotp/LABELNAME?secret=56QHGD211GASYN2FOCBB3PSDSMQML2L

without the counter=0 I can add generate a QR-Code for authy.

Q29udGVudC1UeXBlOiBhcHBsaWNhdGlvbi9wZ3Atc2lnbmF0dXJlOyBuYW1lPSJzaWduYXR1cmUu
YXNjIg0KQ29udGVudC1EZXNjcmlwdGlvbjogT3BlblBHUCBkaWdpdGFsIHNpZ25hdHVyZQ0KQ29u
dGVudC1EaXNwb3NpdGlvbjogYXR0YWNobWVudDsgZmlsZW5hbWU9InNpZ25hdHVyZS5hc2MiDQoN
Ci0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9uOiBHbnVQRyB2MQ0KDQppUUlj
QkFFQkFnQUdCUUpVOWlkUUFBb0pFQkJoWkZVdWpZRkpKSVFQL1JkdVpJSmFocGErN2ZoVlh4bThL
cnF3DQpGczNQMzVsZVh2Rkd5aW1oTjNwN2FkUlEybTAvcWtVRXd0UjNjNzV0dVRoWHdxU3hxTGhr
VG02Z2c4Z2tHMjREDQpIdFdRdWhvNEF4YnNpaVd3dDUybGZJcHpVSGVNb3prN0Rya2FSRDVKRkxI
UzNNSjBod040dngwS1Vld00xcnN2DQpFU1BuSzd6R3R2L3BkUjVwUEdOY1YxckYrQXpISXFDc2FM
UmtvM2Z5VFY3OU1UcHdBUWhFOHJTNkRZSlJQaTlRDQpkdXltQk44SC9RU3N1STArL1JnUXY0dVBN
TXhUNkJrM0xaWmsrUThEQ3N3R1JiMVRFdFQzcFB3TUdkWmx0cUMxDQpBSlFRRnY0MjRkWUlXN3p2
eUJ6RGxOVGkwZDBoTzdLcFIzTWdIQWVVZ1JmV0krazd2SThyY3ZxSEx4RlNmeVRlDQpsVFZlRW1p
ZmtpMmNzOFBBQ1NNbk9ZRmZrdUdkY05Iai9Ha0RDN0lIa1hyTnJMbk51ekdnSWFLTFpTZFBQN1pm
DQprNDFoYmJmSml0NDZkdTB5ZmtHbURqQXJHRk9nQStITnVBT0Q0SXBoK1d2d2l5czlZbU9yN0RZ
RkFqVFExTm1lDQpSOW5lalFMaUVFbXVxZUFTR3NNUEp5MG15U2Z4cG00ZXdmVVhMTitOWnk5czRa
eC9PbWp4Snc3NDNTK2tOcC9QDQpYeUhKMTVCNmJUdmlhOHBlRGVRRERMMjVtR015SVVselo1Rnkx
UmM2cEFUYmxDbS9FS2VKaFpLK3lrUTRYKzZxDQpKUCtOU0daUnErS2UrS2Jab09wUjRtMHF3bE11
TWFWMFpCenFsS2hXNzBKd3AzdUE4aTdUSGwzS0ZvaUROTTgxDQpOcE13ZitOWDdqQkhYYmNuSk41
Nw0KPXlaaEcNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K

Hi Stefan,

1st: thanks for the patience and your support to get this going!

2nd: No, there is no selfservice…

…in fact it is the very same Web UI. :wink:
I realized, that using the same WebUI produces less code and thus
hopefully less bugs. There are still enough bugs anyway.
OK, the normal user can log in to the very same UI using his
username@realmname.

(In the system config you should set the "split @ sign config entry)

Then the user can authenticate with his password from the userstore. In
SQL this is a bit difficult, since each SQL table could store the
password in a different way.
With OTRS it works with my installation :wink:
When the user has successfully logged in to the “selfservice” the
encrypted JWT, that he is passed by the server, contains the ROLE=user
and his username and realm. As he sends this JWT on each request, the
system can determine, that he is “only a user” and thus provide

  1. only his own tokens and
  2. only audit entries, that belong to him and
  3. restrict access to other resouces.

Disclaimer: User in the non-default-realm will not work correctly. I
just added the missing information in the jwt.

There are also plans for the users to be able to authenticate with an
OTP device against privacyidea
add policydecorator for check_webui_user · Issue #95 · privacyidea/privacyidea · GitHub
thus the user would need two factors to login to “selfservice”.

If by any chance you are on the Chemnitzer Linux-Tage you might come
along. There is a stand in the exhibition with privacyIDEA.

Kind regards
CorneliusAm 03.03.2015 um 08:18 schrieb Stefan Steuer:

It works fine! :slight_smile:
My last question :smiley:

Is there a self service for the users so that the user can enroll his
token by himself and create the QR code?

On Monday, March 2, 2015 at 10:49:24 PM UTC+1, Cornelius Kölbel wrote:

yes, fixes this, too.
Good night.
Am 02.03.2015 um 22:32 schrieb Stefan Steuer:
> I'll try it in the Morning ;-)
> Should that File also fix the Problem while Creating a Token for
a User with "umlaut"?
>


You received this message because you are subscribed to the Google
Groups “privacyidea” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to privacyidea+unsubscribe@googlegroups.com
mailto:privacyidea+unsubscribe@googlegroups.com.
To post to this group, send email to privacyidea@googlegroups.com
mailto:privacyidea@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/privacyidea/2598a11d-e265-40c2-bad3-de19496a33d0%40googlegroups.com
https://groups.google.com/d/msgid/privacyidea/2598a11d-e265-40c2-bad3-de19496a33d0%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.

Ok so i reproduce it with some other users and tokens.
When I use the token for the first time - it works… but not a second
time… I have to create a new QR-Code/TokenOn Tuesday, March 3, 2015 at 7:27:55 PM UTC+1, Stefan Steuer wrote:

When I take the Token for the first time it works fine. When I logged out
and want to use the new token (after 30 seconds) I’ll get the error.

You know, that the google app for the windows phone is the newest?

Do you have a URL example, that works with the windows phone?

You can set the tokenlabel in an enrollment policy.Am 03.03.2015 um 09:08 schrieb Stefan Steuer:

Which mobile App do you prefer (except google auth) ?

btw: when I try to scan the code with the google auth for windows
phone I’ll get message that “Der eingescannte Code enthält keine
gültigen Daten für das Konto und den geheimen Schlüssel”

You received this message because you are subscribed to the Google
Groups “privacyidea” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to privacyidea+unsubscribe@googlegroups.com
mailto:privacyidea+unsubscribe@googlegroups.com.
To post to this group, send email to privacyidea@googlegroups.com
mailto:privacyidea@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/privacyidea/fa96b256-52bd-4044-aa21-b8925573b605%40googlegroups.com
https://groups.google.com/d/msgid/privacyidea/fa96b256-52bd-4044-aa21-b8925573b605%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.

oh no - you can add any serviceprovider who’s using 2FA. They support also
modules who support google auth.On Tuesday, March 3, 2015 at 9:33:07 AM UTC+1, Cornelius Kölbel wrote:

Wait, I think the authy app could only be used with their service!

Am 03.03.2015 um 09:25 schrieb Stefan Steuer:

I created for all users TOTP and the error message appears :frowning:

On Tuesday, March 3, 2015 at 9:24:22 AM UTC+1, Cornelius Kölbel wrote:

To me it sounds the same.

Try TOTP instead of HOTP.

Kind regards
Cornelius


You received this message because you are subscribed to the Google Groups
“privacyidea” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to privacyidea...@googlegroups.com <javascript:>.
To post to this group, send email to priva...@googlegroups.com
<javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/privacyidea/c3ac0742-738e-40da-a927-70c530e4dbf1%40googlegroups.com
https://groups.google.com/d/msgid/privacyidea/c3ac0742-738e-40da-a927-70c530e4dbf1%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

any idea? The system is now productive since 7pm.On Tuesday, March 3, 2015 at 7:58:03 PM UTC+1, Stefan Steuer wrote:

Attached you’ll find some screenshots of my settings and some other bugs

On Tuesday, March 3, 2015 at 7:37:38 PM UTC+1, Stefan Steuer wrote:

Ok so i reproduce it with some other users and tokens.
When I use the token for the first time - it works… but not a second
time… I have to create a new QR-Code/Token

On Tuesday, March 3, 2015 at 7:27:55 PM UTC+1, Stefan Steuer wrote:

When I take the Token for the first time it works fine. When I logged
out and want to use the new token (after 30 seconds) I’ll get the error.

Which mobile App do you prefer (except google auth) ?

btw: when I try to scan the code with the google auth for windows phone
I’ll get message that “Der eingescannte Code enthält keine gültigen Daten
für das Konto und den geheimen Schlüssel”

To me it sounds the same.

Try TOTP instead of HOTP.

Kind regards
CorneliusAm 03.03.2015 um 09:23 schrieb Stefan Steuer:

So I got the windows app running. The problem is that the windows
google auth doesn’t support one time password but time based password :smiley:

Maybe you can help me with the error from the App “authy” ?

You received this message because you are subscribed to the Google
Groups “privacyidea” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to privacyidea+unsubscribe@googlegroups.com
mailto:privacyidea+unsubscribe@googlegroups.com.
To post to this group, send email to privacyidea@googlegroups.com
mailto:privacyidea@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/privacyidea/0b2a5fee-1811-4a37-a2e2-5a83e713315e%40googlegroups.com
https://groups.google.com/d/msgid/privacyidea/0b2a5fee-1811-4a37-a2e2-5a83e713315e%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.

Q29udGVudC1UeXBlOiBhcHBsaWNhdGlvbi9wZ3Atc2lnbmF0dXJlOyBuYW1lPSJzaWduYXR1cmUu
YXNjIg0KQ29udGVudC1EZXNjcmlwdGlvbjogT3BlblBHUCBkaWdpdGFsIHNpZ25hdHVyZQ0KQ29u
dGVudC1EaXNwb3NpdGlvbjogYXR0YWNobWVudDsgZmlsZW5hbWU9InNpZ25hdHVyZS5hc2MiDQoN
Ci0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9uOiBHbnVQRyB2MQ0KDQppUUlj
QkFFQkFnQUdCUUpVOWllY0FBb0pFQkJoWkZVdWpZRkp4Ym9QLzFoTm5pNDRaUTY3b0lQM2Vhb3oz
bE9hDQpCUkNQbDJlUExtaXYrR1JSWWYyNDBOYnlwb2dtU2Y3dkxwdUl3M2lKSDdRMnpoL3dhVkRI
ZHd5bkxzeEo5VmpHDQpndlNCdGhxM3BsR0lCanIxWS9mY2NUUVBCVVBxazg0ZWV5aHE0Q1Rub045
Unk0NUxGdVdmc1hXVUUvQ1BsaHR5DQpNM0lwOStTTCt0ZXJEcE9LV3RvK2Vzb01xRjd0YS9QUmdz
eXp1TVk0TnVvbENVRzNJeGV1RlBlUUI1OWRwcU5VDQpPdkpUQlJZQXZHUG5UUGRPZkJBMnJEVUZG
c3dIcnpCeVhCbmU0SFN3NUMvS0s2UkRnVEhFS0E5UmdQdVdYbk5TDQpwQmdubHkrdmxiNzJzY05G
L2VBdGo2cDVzU0czem0rOG9JQzJwNjlPSEdiVkdPbllpQWgrWmloYTk2eFlPeG0vDQpQcGVibnln
TkQ3ZE12VXFlZ1JLNkljUFFOK3pBak1uQ2M5NmRyalcyZUU2VXNCUlFhY1JSNGM2WU0vU1AyazhQ
DQpBTnhHS0srZXdhM2EyaVJ2L1FuZ08zcTBiRHhUN3B6Vlo3eUI0TVg4UE9jZTExMFZCZDVJL2JD
WmNJd3JHMjM5DQpKTkxvZmRmWXkyOWRVWHlBS3VTQTNoU3pScTEyTlZQYWhlTTVBVkdVQlB6LzB3
VkFDdzlYNzhJdFlsMFdrMFYrDQpxTmdiRnZmTFF3ekdrdTAvcUlMd2hGTlR3ZDAxNnpjMDhsd3Bl
dzgyQzBHSmJncy85SVlnL2hWbWV0Nk5kMlVVDQpDUWN4QW9YS0xaNTBhRkMyaVppdDQyeklPYzFU
WDJnM0g3VUU4SWh0SHM2Tmk2dEF1bEc0Q0ZTTm55RW5BOEJLDQpHY280UXdXZzN1YU9oWFEvYmRE
Lw0KPUFMVmoNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K

Hi Stefan,

although you said you enrolled the tokens, for completeness here is the
information:

There is a database table “token” and a database table “tokeninfo”.
The table token contains the basic token data like

  • serial number
  • assigned user
  • secret key…

The table “tokeninfo” contains additional information specific to the
token type.
The TOTP specific information like timeWindow or timeStep is stored in
the tokeninfo table, with the “Key” = “timeWindow” and the corresponding
“Value”.

Thus you could update the tokeninfo table and set Value=180 where
Key=timeWindow.

Kind regards
CorneliusAm 03.03.2015 um 22:33 schrieb Stefan Steuer:

Can I reconfigure the timewindow to 60 for all in the db or do I have to create new tokens/re-enroll them?


Cornelius Kölbel
@cornelinux
+49 151 2960 1417

NetKnights GmbH
http://www.netknights.it
Landgraf-Karl-Str. 19, 34131 Kassel, Germany
Tel: +49 561 3166797, Fax: +49 561 3166798

Amtsgericht Kassel, HRB 16405
Geschäftsführer: Cornelius Kölbel

Q29udGVudC1UeXBlOiBhcHBsaWNhdGlvbi9wZ3Atc2lnbmF0dXJlOyBuYW1lPSJzaWduYXR1cmUu
YXNjIg0KQ29udGVudC1EZXNjcmlwdGlvbjogT3BlblBHUCBkaWdpdGFsIHNpZ25hdHVyZQ0KQ29u
dGVudC1EaXNwb3NpdGlvbjogYXR0YWNobWVudDsgZmlsZW5hbWU9InNpZ25hdHVyZS5hc2MiDQoN
Ci0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9uOiBHbnVQRyB2MQ0KDQppUUlj
QkFFQkFnQUdCUUpVK0ZMT0FBb0pFQkJoWkZVdWpZRkpqcU1QL2lRWkFaL252Qy9NRWVNN0VTK0NL
Yzc2DQpnZjBQQUsrdkdLSEJNa0RFeUlOSHhCMmdnRlVHRDFTT0hVaWsvUUxVRmNtZVN5WW96Z1J3
U05kR05TK25VY3hyDQphSnY0QUp1NTJnb0s2eDlUNDBpZVBnbms5UDB3Z2NvcU9zaUhVR09ic2hL
eWVJcnZtN1BhbExDVHZyNU5lREtuDQpGdTZqUHB5czNaeGlRa0NwTEVjNWR3ZjM3TUwxZDBpSzlE
MFRybzRCQVNSUGk5TkEwZ3RJbTZIdjY0YzNEcXB1DQoyY2h4NEI1UTBZM1JQSjVtZzNaMjlwaUVU
Nzg2N1JxbFEvZmFsekxOUGxOdjI5WFk1V1ArbVhGZFdmMExkRWk5DQpNZUdDd0lDTEpJNURuSTdu
L2tCYVlVRWN4MzQ1STdoMTM5UFp4SGQ5dm5QbVNZeUxFN1BldHlXejd2bG1Zb0t5DQoyRGxONkJF
QmNyNldSU0VZdXUwa3hSUm1LSEpYZWVEeUFaN3BxZmJVTXZVK1FVZWNldkIyMTdkZnpKMzZYRmRD
DQpOakF5VUtodzZrRXQycTdCRFZJSnFsdkRLRXg5bFkxU2Z5bDRscTBRZDB4OElTa2Rhc0hjTHhh
Z1hRUk5HNDI5DQpVZmJjR0hab1NqVVFzNkhuZW9naGpsaHV6SGpESURvOHVFMFQ1V29oelphb2Ns
UlIvaW9OVnZ0djNtNG9JajEyDQpYcDNnUlN0R0ptUitEQlBJZngvR2hTMys5RGRoUFRoTEpGWW5X
cjgxMGNOTjVWQmFMNlRScTA2cnkvMzl4WUJ0DQpGZ3pOLzgrUS94dUExdGp1a0EyT1JpSlcwSXpM
Yjk4TjluQjN1T3hJYlo2UmJUR0M4WnZsTzc2eVlUNEJMUXp6DQpTaG14UkhTQ3JqUXBCSGNRR0w3
Sw0KPUlYUGcNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K

Hi Cornelius,
is it possible to create a second field e.g. in OTRS so that the user has
to enter his password e.g. from LDAP or mySQL AND the OTP?

Username:
Password:
OTP:

Dear Cornelius,
please can you tell me in which file can I delete some entries of this list?

The user should not see all the options ;)On Tuesday, March 3, 2015 at 8:33:43 AM UTC+1, Cornelius Kölbel wrote:

Hi Stefan,

1st: thanks for the patience and your support to get this going!

2nd: No, there is no selfservice…

…in fact it is the very same Web UI. :wink:
I realized, that using the same WebUI produces less code and thus
hopefully less bugs. There are still enough bugs anyway.
OK, the normal user can log in to the very same UI using his
username@realmname.

(In the system config you should set the "split @ sign config entry)

Then the user can authenticate with his password from the userstore. In
SQL this is a bit difficult, since each SQL table could store the password
in a different way.
With OTRS it works with my installation :wink:
When the user has successfully logged in to the “selfservice” the
encrypted JWT, that he is passed by the server, contains the ROLE=user and
his username and realm. As he sends this JWT on each request, the system
can determine, that he is “only a user” and thus provide

  1. only his own tokens and
  2. only audit entries, that belong to him and
  3. restrict access to other resouces.

Disclaimer: User in the non-default-realm will not work correctly. I just
added the missing information in the jwt.

There are also plans for the users to be able to authenticate with an OTP
device against privacyidea
add policydecorator for check_webui_user · Issue #95 · privacyidea/privacyidea · GitHub
thus the user would need two factors to login to “selfservice”.

If by any chance you are on the Chemnitzer Linux-Tage you might come
along. There is a stand in the exhibition with privacyIDEA.

Kind regards
Cornelius

Am 03.03.2015 um 08:18 schrieb Stefan Steuer:

It works fine! :slight_smile:
My last question :smiley:

Is there a self service for the users so that the user can enroll his
token by himself and create the QR code?

On Monday, March 2, 2015 at 10:49:24 PM UTC+1, Cornelius Kölbel wrote:

yes, fixes this, too.
Good night.
Am 02.03.2015 um 22:32 schrieb Stefan Steuer:

I’ll try it in the Morning :wink:
Should that File also fix the Problem while Creating a Token for a User
with “umlaut”?


You received this message because you are subscribed to the Google Groups
“privacyidea” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to privacyidea...@googlegroups.com <javascript:>.
To post to this group, send email to priva...@googlegroups.com
<javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/privacyidea/2598a11d-e265-40c2-bad3-de19496a33d0%40googlegroups.com
https://groups.google.com/d/msgid/privacyidea/2598a11d-e265-40c2-bad3-de19496a33d0%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

Q29udGVudC1UeXBlOiBhcHBsaWNhdGlvbi9wZ3Atc2lnbmF0dXJlOyBuYW1lPSJzaWduYXR1cmUu
YXNjIg0KQ29udGVudC1EZXNjcmlwdGlvbjogT3BlblBHUCBkaWdpdGFsIHNpZ25hdHVyZQ0KQ29u
dGVudC1EaXNwb3NpdGlvbjogYXR0YWNobWVudDsgZmlsZW5hbWU9InNpZ25hdHVyZS5hc2MiDQoN
Ci0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9uOiBHbnVQRyB2MQ0KDQppUUlj
QkFFQkFnQUdCUUpWUDUxTkFBb0pFQkJoWkZVdWpZRkpmaHNQL2k1b2k2MW1EYUJvc1JLNlFRMW8y
NHpKDQozZ2FwTUxIaGRVSm8rMkczMFA4T3NJRlBmRVQ0VUJMejl4eWcxeHZJN2VwWnlORmRiY3NT
R2hMOTNVUkdQZHlYDQprbGNadWcrM01adHZ5NjBia2tKN3ZZNHhVMUxHaFRwVDl1bjl0SXZvd2Fs
L1RFQ3ZNYkpRT01CN3JxNzc4dzFmDQp0MkgzOFdUUm1DcWJScG1aaXgzV2NzUDg4ekhhV3lWLytF
dXFPa1NjL3RjbG5wU0dDK3hLcSt0M1FlR3Y2VTR6DQpFZFE4L2l3VENidFZncm5VZ3JWTDJTdE1m
VzFReHErVGp2QVRRcFFDZ0FKZHpBc3J2Rmx6Ty90RUtsZmFjTUlHDQpWa0tnTFJ5blVzUFJkbkcz
ZXd3YUN4RW1vTVRUVlhZeEY1STE0TkNXK2J6WnBnbElITmVtMjFOSkdKb2F1OVRNDQpSQ1ZOUE13
L2IydXNQN01ndjN5MklmQlJocWJRZEVpeXVSRVNTR2hsSzRGTUJYSndQRXlYUU5YTy9rZnp3alJs
DQpXakFrYlAyS0hSRGVvYnd3MlhadmNqSDF4UVEwQmVjVERJeS9ydEZhMUI1cjA1VzZkYkE2WHNq
c3h2Q2lsTzV6DQpKMER0TFFUWFIwdG5zVXFqTzRGeHMxZW5NUzJkSzNDa3Q2a1IvK2ErYTErZy9q
VHhmaStKM1Y1ZFJtWlFmRi9uDQpxQ21aWHpKcmd6VWcvZ2lENUN4a1NoczY1VDlnVUprT1FNc0pt
TC9pQUpaZzd4TEtUbWtHWXh1VkMwOVpEdUhjDQovUnVjbmw3VHBwd3hRYkplcUhMTXcrNU9EeHdR
NTQrRkllN2RaNE1WN29PZlRwN0RQS0VVL0FhK0pMa0gydEdEDQpyV2k3NnFCT1UzNkwyUkJpT3RH
Zg0KPXB4aVcNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K

Hi Cornelius,
long time ago :slight_smile:

Please can you describe me how I can set the rule, that the PI use the
Password from the LDAP-request and not the password from the mysql?>