Create user in OnBase with AD Configuration

[Ryan_Wakefield]

Is there a way to use the Unity API to automatically create a user inside of OnBase that is tied to an AD account to where you can map a SID to that same user to be created. I am hoping I am just missing the details of what I need in order to accomplish this.

Thanks.

[AdamShaneHyland]

@Roger Linhart , no.  This behavior has been around since the implementation of Active Directory - Enhanced (or more specifically when it was named Active Directory) in OnBase 12 to my knowledge.

[Rob_Keberdle]

The dependency on SID existed with the old NT Authentication model, and errors regarding invalid items (due to deletion in AD) would flood the application server.  Roger, perhaps this is what you're thinking of?

[Roger_Linhart]

From our Support Issue # 00301686

Description
Older OnBase User created with Active Directory is being logged on instead of creating a new user with newer information. Prior to the upgrade the user had a legal name change resulting in their Active Directory account being renamed.

OnBase created a new OnBase User with the new AD user name. From this point forward OnBase used the new user name in document history. Since the upgrade this user reports that OnBase has reverted to using their old user name in Document History.

Resolution
After using a template script to clear the Security ID of the original OnBase user the correct account was used.

This issue occurred because the Security ID is checked first for an OnBase user, and there was already this SID on a previous user.

[AdamShaneHyland]

Hi @Roger Linhart , 

For example, if I logged into OnBase with JDOE and SID 1234, then the next time I logged with OnBase would compare the SID 1234 in order to authenticate me into OnBase. 

IF my SID changed for any reason (SID 4312), a new user account would be created (JDOE2). 

IF my SID didn't change (SID 1234), but my username did (JIMDOE), the username in OnBase will update as long as you have Synchronize User Attributes enabled.  This was changed with SCR: #281856 in OnBase 17.

Take care.

[Ryan_Wakefield]

Hey @Adam Shane , I do have one very specific question for you regarding this. While I completely understand the logic above, there are still some really REALLY large gaps to it. So I was wondering, do you know what else (aside from the securityid column) would be required to tie the user account to an account in AD? I am assuming that this column is it, but figured I would ask.

Thanks.