We currently have 10 form participant licenses. If we tie these licenses to an LDAP account, when we upgrade the licenses to a named user license, will it keep the correlation to the forms that were started by the user and also will tasks that are assigned to that user keep the correlation?
Question
Question
Answers
Yes, all the correlation for this LDAP user can be kept when you upgrade its license from participant to named user.
What if it is not an LDAP participant user? Is there a way to link the information from a non-LDAP participant user to an LDAP participant user or named user? Similar to moving from an LF user to an Windows Account in the main Laserfiche application.
It is not supported to migrate non-LDAP participant to named user right now. Forms are working with other Laserfiche products to support central accounts management which will provide the flexibility to change license between named user and participant.
What is the process for upgrading the account from an LDAP participant license to a named license?
We recently needed to do this for a user and I added the named user account in the Admin Console as a Windows Account. The next day the user was able to log into Forms using both accounts, but the users history and access to processes only showed up using the participant license. If I go to assign a user to a user task, I see there are now 2 accounts for that person, one using the participant user (email address) and one using the windows account.
I am afraid of disabling the participant license because I do not want the user to lose all of their history and other tasks.
We are using Forms 9.2.1.1069
Can someone from Laserfiche please let me know how this is supposed to be accomplished?
It would be great if we could get an answer to this question. I think this is something that could come up for a lot of users down the line.
Thanks,
Hi Blake,
I'm not on the Forms team, so I can't answer this definitively, but I suspect the issue is going from LDAP participants in Forms to regular Windows users in the LF Admin console.
Instead, if you add these same users as LDAP users in the admin console, through the LDAP management node, I think it will map correctly.
This is because how how we identify the users: their SIDs. Regular Windows AD users are identified by their AD SID. On the other hand, all LDAP users (eDirectory and AD as LDAP) are identified by a derived SID that comes from their Distinguished Name (DN).
The end result is that the SID used in Forms is derived from the user's Distinguished Name does not match the SID of the user in Windows, so Laserfiche has no way of determining which user is which. On the other hand, if they are added in the Admin Console as LDAP accounts, they will also be assigned SIDs.
Sorry I can't give you a 100% certain answer, but I hope this helps.
Forms identity users using the SIDs. For LDAP participant, Forms generate their SID based on their distinguished name use the same method as Laserfiche Server(When users are added through LDAP profile using AD as LDAP), so the SID for a LDAP user is the same no matter they are added as LDAP participants in Forms or added as LDAP named user in Laserfiche Server.
It has been fully tested that data associated with the LDAP user will be kept when doing migration between LDAP participants and LDAP named users.
Forms identity users using the SIDs. For LDAP participant, Forms generate their SID based on their distinguished name use the same method as Laserfiche Server(When users are added through LDAP profile using AD as LDAP), so the SID for a LDAP user is the same no matter they are added as LDAP participants in Forms or added as LDAP named user in Laserfiche Server.
It has been fully tested that data associated with the LDAP user will be kept when doing migration between LDAP participants and LDAP named users.