Cornelius Kölbel

We should implement this by implementing #1631 Or: please compare this at least to checks e.g. in HOTP or TOTP enrollment. If the otpkey length is checked in different tokentypes,...

@belfhi How long was the description you wanted to add? What are you writing in the description and why? Maybe it makes sense to make the description field longer and...

You mean like here? ~~~~ .state('config.events', { url: "/events", templateUrl: configpath + "config.events.html" + versioningSuffixProviderProvider.$get().$get(), controller: "eventController" }) .state('config.events.list', { url: "/list", templateUrl: configpath + "config.events.list.html" + versioningSuffixProviderProvider.$get().$get(), controller: "eventController"...

Added note in ticket.

We have the serial number of the CA in the token details view. I think this is totally fine. What is your use case? Do you want to search for...

OK, you are right. We have currently the requestID in the tokeninfo, not the serial number. Anyway @nilsbehlen your use case would be interesting.

I think your approach of the PR is not generic and only has your own problem in mind. The implementation is also counter intuitive, since the value is not evaluated....

It is possible to enroll a webauthn token several times in privacyIDEA. It is not clear, that this error message (object-invalid-state) corresponds bidirectionally with an attempt for a 2nd enrollment....

A lot of dependencies with readthedocs are broken. We can only try to fix this for the future.

Still, I do not understand or can reproduce your problem.