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
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.
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)
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)