I’ve encountered some strange behaviour of web ui in PrivacyIdea.
My version in 3.8(the issue was already in 3.7.4 version).
Os is Ubuntu 20.04 LTS.
When I try to register new token I get blank page with ‘Logout’ only button instead of information “The token was successfully enrolled with serial number ”.
See the screenshot below:
if there is a proper page generated after step 3 - revoke and delete token using admin and repeat steps for any user - get blank page.
Earlier before in 3.6 I’ve always get “The token was successfully enrolled with serial number” info.
There is no big deal, because token is registered and active, but still looks like a bug.
My eyes tell me there is step 2 -
1)pre/push the button to generate token
2)token generation&validation
3)post(success/not success)
: 3 different pages at all and pre-page works for step1 and post page works for step2&3.
Templates is ok, I suppose, but question was about pre-post pages behaviour.
POST is the moment, after the token is created internally in the server. POST is the moment – as the docs say! – when the user is supposed to scan the QR code, not AFTER the user scans the qr code.
POST does not mean after the user is done, but after the token is created in the server. In this moment the user is not done, yet.
I am rereading the docs and I think they state it rather good.
Do you have a concrete suggestion at which point how these should be improved?
Or am I misunderstanding you and you might have stumble upon a sideeffect bug? Maybe you can post your screenshots and your policies.
You should also view this video OTP Token Enrollment Wizard - YouTube
which is linked in the docs.
POST is the moment, after the token is created internally in the server. POST is the moment – as the docs say! – when the user is supposed to scan the QR code, not AFTER the user scans the qr code.
Ok, now I understand.
Do you have a concrete suggestion at which point how these should be improved?
So my suggestion is to add some page(like PRE/POST) for validation step when a user must verify created token and POST that means system created token and user verified OTP.
But it’s definitely not critical.
I have no questions more for this case.
Thank you!
You see that your personal POST custom template is imported here:
You can also use token states in your own custom POST templates.
This way you could e.g. do
<div class="text-center" ng-hide="enrolledToken.rollout_state === 'verify'">
Thank you for having successfully verified the token.
You can now turn of your computer.
</div>
So this text will be visible after the user has successfully verified the token and the logout button gets visible.
I don’t want to be annoying, but, please, could you give me a clue how to hide QR after token was verified by user within this code:
<div class="text-center" ng-hide="enrolledToken.rollout_state === 'verify'">
Thank you for having successfully verified the token.
You can now turn of your computer.
</div>
I don’t know JS at all and it looks everything is written with it.
Forget about it.
You would have to modify/overwrite an existing vanilla html template.
It is exlained in the customizing section.
I am not willing to explain or link it here.