1. UNIFYBroker Forum
  2. UNIFYBroker/Aurion
  3. Bugs
0
Not a bug

Aurion Security User not set on export

Sean Little 6 years ago in UNIFYBroker/Aurion • updated by Adam van Vliet 6 years ago • 5

Hi Guys,

We seem to have uncovered a possible bug with the Aurion connector. We have 2 issues with our solution - firstly that the OsUserId on the Aurion Security User is initally populated with an incorrect value (not an IDB issue).

However, when the solution attempts to update this value with the correct value (as set n AD), it does not appear to persist in Aurion.

The export is lined up as an update, and successfully exports from the MA through IDB without error, however the value is not actually set on the Security User object within Aurion.

A subsequent delta import results in an exported-change-not-reimported error on the MA.

The environment is using IDB v5.3.1 and communicating with Aurion v11.4.6

We will also provide the version of the Aurion connector soon

Cheers

Sean/Richard.

Answer

Answer
Not a bug
Adam van Vliet 6 years ago

Updated the field name casing for OSUserId to OsUserId.

GOOD, I'M SATISFIED
Satisfaction mark

Thanks,

The customer has just advised that this has resolved the issue.

Satisfaction mark by Sean Little 6 years ago
Under review
Sean Little 6 years ago

Hi Guys,

As mentioned, the Aurion connector is version 5.3.0.0.

Thanks,

Sean

Curtis Lusmore 6 years ago

Hi Sean,

Has this issue occurred consistently since installing the connector, or has this only recently started occurring? If only recently, has anything changed in the solution or the environment around the time the issue started occurring? Does this occur in more than one environment, and is it reproduceable in an environment you can easily test in (quick ability to apply patches, access to network tracing tools, etc.)?

Sean Little 6 years ago

Hi Curtis,

Apologies for the delay in response. I have passed these questions on to the customer and am currently awaiting a response. I will let you know when I receive one.

Sean Little 6 years ago

Hi Curtis,

I've just heard back from the customer. The issue has occurred consistently since project close, there have not been changes in the solution or environment around the time the issue started occurring, the issue also appears in their Test environment but appears to be working correctly in DEV.

Would it be worth requesting the configuration for DEV as well?

Answer
Not a bug
Adam van Vliet 6 years ago

Updated the field name casing for OSUserId to OsUserId.

Customer support service by UserEcho