I have one source telling me that once we update our backend of Advanced Authentication to 6.4.2, any previous bluetooth device enrolled as an authenticator, needs to be re-registered again in the Self Service portal in order to be used as a bluetooth esec authenticator. This concerns Windows clients.
Any thoughts on this?