Special syntax for where-statement?

Hi Cornelius,
as you see I’m working with PI intense :wink:

Is there a special syntax for the where-statement in the SQL-resolver?

I tried some different formats without success.

e.g.

id = 3
users.id = 3
WHERE users.id = 3

when I click on the test-button I can see the same number of users on every
time.

Hi Cornelius,
I tried it on several system but with no success.

Error log:

[2015-05-05
18:36:38,173][2776][140296524211968][ERROR][privacyidea.lib.user:487]
ValueError(‘need more than 1 value to unpack’,)
[2015-05-05
18:36:38,182][2776][140296524211968][ERROR][privacyidea.lib.user:488]
Traceback (most recent call last):
File
"/opt/privacyidea/privacyidea-venv/local/lib/python2.7/site-packages/privacyidea/lib/user.py",
line 477, in get_user_list
ulist = y.getUserList(searchDict)
File
"/opt/privacyidea/privacyidea-venv/local/lib/python2.7/site-packages/privacyidea/lib/resolvers/SQLIdResolver.py",
line 463, in getUserList
(w_column, w_cond, w_value) = self.where.split()
ValueError: need more than 1 value to unpack

Q29udGVudC1UeXBlOiBhcHBsaWNhdGlvbi9wZ3Atc2lnbmF0dXJlOyBuYW1lPSJzaWduYXR1cmUu
YXNjIg0KQ29udGVudC1EZXNjcmlwdGlvbjogT3BlblBHUCBkaWdpdGFsIHNpZ25hdHVyZQ0KQ29u
dGVudC1EaXNwb3NpdGlvbjogYXR0YWNobWVudDsgZmlsZW5hbWU9InNpZ25hdHVyZS5hc2MiDQoN
Ci0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9uOiBHbnVQRyB2MQ0KDQppUUlj
QkFFQkFnQUdCUUpWU05OWEFBb0pFQkJoWkZVdWpZRkp4djBQL2lzTVgwUkZmSy9ueWtCbVhsb3Bm
N2p0DQpFVmh4cWFtRXgrNnN6UFJFb2M1eXV0L3pDS1JWTUxHNFBuUnlkWlM4Z0c5MS91QUtodUgv
L0FhemY2U1RlRDFGDQo4ejU0eVl0ZzVtdnk3Q2xJRXBCbzF2TXVaeTFiNE9QbU1sT2xoTjY4N0ZU
SHdscTF5ZEZnWXpvMkE0NWQ0MTFIDQpsMmRIMDZxbFI5VlVpaUdld1B1NnpHODE2OURSdWJOR2lD
eGZqZlgwQ05ITTVYcGhFZ3l3RURaaGg2S2RZMk9PDQpQSUdQbi9BZnBqWjZhVzR3Ym1lZ01VNzFE
TlVSMFVhYU1iS2lzUm1JMGgxbjhSYjd6dVNjc05JYVVVTDRoOVhkDQorRFN3Y0pGWDE0MzRKM1lj
UmNkVFFXallCcEY0clZFSFFNNHhJVWhwTGhLV3c0TG1JYTVYeUd2bGxaY2s5M3V3DQpRNW9QSFRH
RitWbmRJZDZyVXZrUmpqdDZ1TWlBNUhtaUlGRkN6bEdqeWh4ZUlMcGtuNnRnNUtGU3BPS3F3ZGU3
DQpBL0RCc3l6ampZejB3blA4amxkR3BOeEI4d1UvemVwcDNoOHVqcEs3bGx2L0JmWVBsQ1NwN1J4
RlBFMGVEWkNBDQo2aEVLZmRoQk1qYVREOUozT29Way9uY1RHankxOEFqVzNFcDVjdUJxeldVNzIv
Y0hjQXVmY05jL0hpcG9yRmJFDQpVV0hwM1hUSmh6NVY4WXRSTG96OXFEazQ5SVhXTUQwcWZwazV6
dEpXaks4aW5ITnVwaWIzWVpHaiswSlR2N2xjDQpJT216czg1T3VhWVJENURkT1JZNlQ4M2pGVEZk
MVA0bWxDZXV4QW5uZ2pCVmxoL05OcndnYW5GeFRqUnkxcG9pDQpRTURKMkxEZTQ2OUJWM29VUjNU
Lw0KPUZuNzUNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K

Q29udGVudC1UeXBlOiBhcHBsaWNhdGlvbi9wZ3Atc2lnbmF0dXJlOyBuYW1lPSJzaWduYXR1cmUu
YXNjIg0KQ29udGVudC1EZXNjcmlwdGlvbjogT3BlblBHUCBkaWdpdGFsIHNpZ25hdHVyZQ0KQ29u
dGVudC1EaXNwb3NpdGlvbjogYXR0YWNobWVudDsgZmlsZW5hbWU9InNpZ25hdHVyZS5hc2MiDQoN
Ci0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9uOiBHbnVQRyB2MQ0KDQppUUlj
QkFFQkFnQUdCUUpWU1AxQkFBb0pFQkJoWkZVdWpZRkovR0lQLzFsb00rK0NOQUV5ZGpmY0g2Z1hn
Z1ZGDQpPWDd6OXU0NU9iSFU0SU1XM0Z2c2xNWlZnOTdZTmpFeWx1OWNKeDZBRDhnS0RUbWNuWW5y
MFN2akpVY3Y1NHI0DQpuT0grUHlCQVdoUDhKbHpuVnBZTjF1QW1wN2tXS0JyQ1dtRDBmckpiZDYv
YUdZUnJPR0ZRRTAyY2tXbGFYcFdiDQp5SDN1TEFGS3JNR3F5NFNwVDhKcWg2MGc4ZUJlb3ZQS045
K2ZibEpsSHQ1ZWZVa3N6Mit6Z0F2ck8rMFQzRW9oDQpyOXllOXpzS0xJYTdwYktJU2FKSXUyQ0t6
L0w3KzFLb0dRVDVpamZkSDFBUlRaMW5TUXJkYVBKem0ybkpGOHozDQoySklDcXFrZWRmaFcxT24w
MGQxRlJwMlRKblJ3UXhKZlMwWHJMcjg2ZFJvbU5mdFZyNEdtbjF4bjBSSmlrTEthDQovTElYWkdS
aWNNU09XdjQ3MlVkd0lkQkR2MVNTTFpMSTBmbFZwOFY4UlJYNlJHSk1BbVdkaFBhcTI0T3k1dzdv
DQpqZENabjM5S1ZZZkNybW1IVnF3a2dBbVd5SmtrVnYzUThnWVVOUGtmQ0JRcGlPaC95dHFIa0h2
c2Y4WkxQYzhnDQp5RzRWc2N0S0tDLzBnL25Ea0hwZE92S0NDOWZhcVZWd2Y1eS9NYS83ZHpIb1Rk
YTh2WHRjdWFUclhLcld4Z3FWDQpWU3YwUFZkVUxRMk4vTlRZenZnWFM2M0pqN3ZwYUx1Q3RlQ2d2
Nnl1OGtsQTZsN3RYdG5kQ2g1QWpFNUJ2RXJhDQp2NEV1aG9sTExhaTVYNmdBVjBpNERGZzBFNCs3
V09maUtwSzluVERGWVJNTFVhL3Jrd242d0NXb00vVEN3SnY3DQpFcENyRXdYMnFXbytXYUtKai85
Sw0KPWk1Sm8NCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K

Hi Stefan,

you are right.

This should not be a big deal.
It is located in:

self.where is used in getUserList.

But it should also be used in getUsedId and getUserInfo.

I will create an issue for this.

Kind regards
CorneliusAm Mittwoch, den 03.06.2015, 01:40 -0700 schrieb Stefan Steuer:

Hi Cornelius,
is it possible to separate the query strictly with the
where-statement?
In the moment the where statement is to separate the user-liste in PI

  • but during the authentification PI is trying to find the user in the
    db.


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.
To post to this group, send email to privacyidea@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/privacyidea/1f12347b-35d2-431a-a96a-dd353f45ebc4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

signature.asc (819 Bytes)

Sounds good!
When this “issue” is resolved - it would be easier for an admin to choose
multiple data-sources (AD, SQL, …) to authentificate the users against
one SQL (which contains all users of each sources) :slight_smile:

Hi Cornelius,
is it possible to separate the query strictly with the where-statement?
In the moment the where statement is to separate the user-liste in PI - but
during the authentification PI is trying to find the user in the db.

Hi Cornelius,
I’ll hope you’re well - Are there any news regarding this feature? :)On Wednesday, June 3, 2015 at 10:50:25 AM UTC+2, Stefan Steuer wrote:

Sounds good!
When this “issue” is resolved - it would be easier for an admin to choose
multiple data-sources (AD, SQL, …) to authentificate the users against
one SQL (which contains all users of each sources) :slight_smile:

Great :slight_smile:
Is there already a release date and an update-guide available?