From: Willem E. <wi...@cl...> - 2018-12-11 13:17:49
|
Hi Krzysztof, we are trying to upgrade our unity instance to a recent 2.x version (2.6.x preferably). The upgrade from 1.9.6 to 2.0.0 seems to go fine, but then upgrading to 2.4.0 or anything higher results in users without password. As far as I can see in section 4.2.4 of the upgrade documentation there is no specific action required with respect to existing password, even though a new sys:password credential has been introduced. I've also noticed that on a fresh 2.4.0 test installation our admin user is requested to update the credential because of the credential requirements. In our 1.9.6 installation we are using a custom password credential, but this is included in the database export: ... { "id" : 10, "name" : "sys:Credential:Password credential", "contents" : { "flags" : 3, "maxElements" : 1, "minElements" : 1, "selfModificable" : false, "uniqueValues" : false, "visibility" : "local", "syntaxState" : "{\"regexp\":\"\",\"minLength\":0,\"maxLength\":10240}", "displayedName" : { "DefaultValue" : "sys:Credential:Password credential", "Map" : { } }, "i18nDescription" : { "DefaultValue" : null, "Map" : { "en" : "Credential of Password credential" } }, "metadata" : { } }, "valueSyntaxId" : "string" } ... With the log level on debug there is no clear indication of any issue during the database restore or server startup. I assume this credential definition gets imported as well. Is that correct? When trying to log in we get the following error: DEBUG unity.server.PasswordVerificator: The user has no password set: admin DEBUG unity.server.PasswordVerificator: The user has no password set: te...@cl... Any idea what could be the issue here and how we can solve this? Best, Willem |