Hmm looks like the application hasn't authenticated to the token yet. If you didn't get a password prompt, then you most likely have an application problem.
Well, if the way you need to interact with the dabase changes after enabling the FIPS mode, isn't this a regression?
Note that the created database is using exact same password in fips and non fips mode, in fips mode the application fails, while in non fips it works correctly (recognises the certificate).
> Well, if the way you need to interact with the dabase changes after
> enabling the FIPS mode, isn't this a regression?
No it's NSS as always done this in FIPS mode. Applications which can't authenticate arbitrarily are not FIPS level-2 compliant. If the database does not have a password, that's a different matter.