The token was successfully enrolled with serial number - empty page

Hi, all!

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:

Steps to reproduce:

  1. logon with ldap user
  2. click ‘Enroll Token’(TOTP)
  3. scan QR and paste ‘Client Part’ information

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.

No error messages in privacyidea.log.

Restart Apache2 services once and check if works.

No, the same result.

My educated guess is that you are using the enrollment wizard.

Then this is the expected behaviour!

You configured html templates are not at the correct location.

Yes, I use TokenWizard policy.
I didn’t even know about such feature with custom pages.
Thank you!

1 Like

https://privacyidea.readthedocs.io/en/master/faq/customization.html#tokenwizard

But what if I have 3 pages to customize:

  1. PRE - before click Enroll Token
  2. ??? - token verification/validation using client part/otp
  3. POST - token enrolled successfully.

When I use POST it appears at step 2(surprisingly) & step 3(as it supposed to). It there way to use different page for step 2?

Why do you think, there is a step 2?

Read 16.1. Customization — privacyIDEA 3.8 documentation

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.

Again my often educated guess is that you use the verify_enroll policy. This might lead to that you are a bit confused.

The docs say there are two steps. Not three!

https://privacyidea.readthedocs.io/en/master/workflows_and_tools/enrollment_wizard/index.html#customization

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.

Thank you for your patience.

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!

Compare this existing template:

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.

Ok, I’ll try this, thanks a lot!

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.

Ok, thank yor for the asnwers.

Ah, I already posted the link, how to modify existing templates.

https://privacyidea.readthedocs.io/en/master/faq/customization.html#templates

Question is closed, cornelinux, thank you and sorry for stupid questions.