Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing token fails with setrealm policy present #1943

Open
cornelinux opened this issue Nov 27, 2019 · 0 comments
Milestone

Comments

@cornelinux
Copy link
Member

@cornelinux cornelinux commented Nov 27, 2019

Top-level intent

Test a token in the UI.
Testing a token in the Web UI triggers a request like

https://privacyidea/validate/check
serial=PISM1234
pass=1234

When a setrealm policy is set, than the request will be modified to

https://privacyidea/validate/check
serial=PISM1234
pass=1234
realm=somerealm

This will result in an error "user can not be found in the resolver", since privacyidea thinks there is a user object User(login="", realm="somerealm") and can not find an empty-string-user.

Steps to reproduce

s.o.

Expected outcome

Testing the token should work ;-)

Configuration

This only happens when a setrealm-policy is active.

Possible ideas

I am currently not sure how to address this, if we should

  1. find the user and fill in the user
  2. only do the setrealm, if a user is contained
  3. ...
@cornelinux cornelinux added this to the 3.3 milestone Nov 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.