Identity Broker Forum
Welcome to the community forum for Identity Broker.
Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.
Null reference during logging
I am receiving an alert on the home page on my local build when it is browsed to.
If no other log writers are configured, any issues may be missed. The exception details are as follows:
System.NullReferenceException: Object reference not set to an instance of an object.
at Unify.Framework.Logging.ExceptionLogEntry.get_LogEntryModule() in c:\workspaces\DEV\FrameworkCore\Source\Logging\Unify.Framework.Logging\ExceptionLogEntry.cs:line 71
at Unify.Framework.Logging.CsvLogWriter.WriteLogEntryBase(ILogEntry logEntry, String filePath) in c:\workspaces\DEV\FrameworkCore\Source\Logging\Unify.Framework.Logging.Writer\CsvLogWriter.cs:line 61
at Unify.Framework.Logging.CsvLogReaderWriter.<>n__FabricatedMethod1b(ILogEntry , String )
at Unify.Framework.Logging.CsvLogReaderWriter.<>c_DisplayClass19.b_16() in c:\workspaces\DEV\FrameworkCore\Source\Logging\Unify.Framework.Logging.Writer\CsvLogReaderWriter.cs:line 455
at Unify.Framework.ExtensionMethods.WaitOnMutex(Mutex mutex, Action work) in c:\workspaces\DEV\FrameworkCore\Source\Scheduling\Unify.Framework.Scheduling.Job\JobExtensionMethods.cs:line 21
at Unify.Framework.Logging.CsvLogReaderWriter.WriteLogEntryBase(ILogEntry logEntry, String filePath) in c:\workspaces\DEV\FrameworkCore\Source\Logging\Unify.Framework.Logging.Writer\CsvLogReaderWriter.cs:line 459
at Unify.Framework.Logging.FileLogWriterBase.<>c_DisplayClass5.b_4() in c:\workspaces\DEV\FrameworkCore\Source\Logging\Unify.Framework.Logging.Writer\FileLogWriterBase.cs:line 298
at Unify.Framework.ExtensionMethods.WaitOnMutex(Mutex mutex, Action work) in c:\workspaces\DEV\FrameworkCore\Source\Scheduling\Unify.Framework.Scheduling.Job\JobExtensionMethods.cs:line 21
at Unify.Framework.Logging.FileLogWriterBase.InternalWriteLogEntry(ILogEntry logEntry, String filePath) in c:\workspaces\DEV\FrameworkCore\Source\Logging\Unify.Framework.Logging.Writer\FileLogWriterBase.cs:line 299
at Unify.Framework.Logging.FileLogWriterBase.WriteLogEntryBase(IBrandedLogEntry logEntry) in c:\workspaces\DEV\FrameworkCore\Source\Logging\Unify.Framework.Logging.Writer\FileLogWriterBase.cs:line 127
at Unify.Framework.Logging.LogWriterBase.WriteLogEntry(IBrandedLogEntry logEntry) in c:\workspaces\DEV\FrameworkCore\Source\Logging\Unify.Framework.Logging.WinEventLogWriter\LogWriterBase.cs:line 46
Service fails to start if base connector cannot be found
The following is logged on service startup if the base connector cannot be found.
Service cannot be started. Unify.Framework.UnifyServiceInitializeException: A connector matching the id 'bf96de17-ee6f-490a-b3c3-77a18435a734' could not be located. ---> Unify.Framework.UnifyEngineException: A connector matching the id 'bf96de17-ee6f-490a-b3c3-77a18435a734' could not be located.
at Unify.Product.IdentityBroker.ConnectorRepository.GetConnectorSchema(Guid connectorId)
at Unify.Product.IdentityBroker.EventNotifierConnectorRepositoryDecorator.GetConnectorSchema(Guid connectorId)
at Unify.Product.IdentityBroker.Adapter.RefreshColumnSources(IEntityChangeDetector entityChangeDetector, IEnumerable`1 existingChangeProcessorConnectorIds, Func`5 createColumnSourcesFunction, Action`3 addBaseConnectorChangeProcessorAction)
at Unify.Product.IdentityBroker.AdapterEngine.RefreshColumnSources(Guid adapterId)
at Unify.Product.IdentityBroker.AdapterEngine.<.ctor>b__2(IOperationalAdapterBase`2 adapter)
at Unify.Product.IdentityBroker.AdapterAdded`1.Invoke(TAdapterType adapter)
at Unify.Product.IdentityBroker...
Improve architecture of Logging Engine
Please move the extended logging engine into the logging engine and logging engine base.
Please create a generic validation Action that is passed down to the log writer factories, that calls back into the engine. Add a validation routine that confirms the CSV writer doesn't conflict with others.
Additionally, the Identity Broker service (haven't tested console) is halting operation on attempt to browse to the Connector and Adapter page (the Home page is fine, haven't tested others). The following error is being thrown:
Error occurred in module: Logging
Unable to log, exception as follows:
System.IO.IOException: The process cannot access the file 'c:\test20111130.csv' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding)
at System.IO.File.InternalAppendAllText(String path, String contents, Encoding encoding)
at Unify.Framework.Logging.CsvLogWriter.WriteLogEntryBase(ILogEntry logEntry, String filePath)
at Unify.Framework.Logging.FileLogWriterBase.WriteLogEntryBase(ILogEntry logEntry)
at Unify.Framework.Logging.LogWriterBase.WriteLogEntry(ILogEntry logEntry)
Logging configuration attached.
Thanks.
Unify.Framework.Logging.LoggingEnginePlugInKey.extensibility.config.xml
Transformation on Relationship with multivalue return
Is there a transformation that performs a relation lookup that is capable of returning multiple values?
Currently for a client we have two tables, one has a user ID, the other a userID and an organisation name. A single User ID may be associated with multiple organisation names.
The design calls for a single adapter that has a multi value attribute on a person object listing all the organisation names to which that person belongs. The person object is the only object being flowed into the metaverse for this design.
I've had a look at two exisiting transformations:
Relation.Group (https://unifysolutions.jira.com/wiki/display/IDB306/Group+membership+relational+transformation) - This one returns multiple results, but regardless of whether Relation.Group or Relation.Group.Dn is used, the result appears to be a list of references. As noted already, we only flow the person into FIM and thus we want the actual organisation name, not a reference/DN value.
Relational (https://unifysolutions.jira.com/wiki/display/IDB306/Relational+transformation) - This can flow the actual value, but it will only flow a single value and as far as I can see, does not support output to a multivalue field.
I want to check whether there's an alternative I've some how overlooked. The connectors (one for each sql table) is a straight up unify SQL connector based around the EmpopweHR design. There is the option to redevelop this if needed to handle the work rather than an adapter, but an adapter is preferable.
Multivalue DN validator throws an invalid cast error
When attempting to create the correct value during an export, a multivalue DN generator field throws a cast exception:
Unable to cast object of type 'Unify.Framework.MultiValue`1Unify.Framework.StringValue' to type 'System.Collections.IEnumerable'.
> Unify.IdentityBroker.Entity.Schema.dll!Unify.Product.IdentityBroker.EntityMultiValueObjectTypeSchemaValidator<Unify.Framework.MultiValue<Unify.Framework.DistinguishedNameValue>,Unify.Framework.DistinguishedNameValue,Unify.Framework.IO.DistinguishedName>.CreateValue(object dataValue) Line 90 + 0x13 bytes C#
Unify.IdentityBroker.Entity.Schema.dll!Unify.Product.IdentityBroker.EntitySchemaFieldDefinition.CreateValue(object dataValue) Line 64 + 0x39 bytes C#
Unify.IdentityBroker.Adapter.LDIF.dll!Unify.Product.IdentityBroker.LDIFToAdapterEntitySaveAdapterBase<Unify.Product.IdentityBroker.IAdapterEntitySaveChange>.ConvertValues.AnonymousMethod_c(<>f_AnonymousType0<Unify.Product.IdentityBroker.AdapterEntityValueCollectionKey,System.Collections.Generic.List<Unify.Framework.StringValue>> item) Line 143 + 0xe4 bytes C#
System.Core.dll!System.Linq.Enumerable.WhereSelectEnumerableIterator<System.Linq.IGrouping<Unify.Product.IdentityBroker.AdapterEntityValueCollectionKey,Unify.Framework.StringValue>,System.Collections.Generic.KeyValuePair<Unify.Product.IdentityBroker.AdapterEntityValueCollectionKey,Unify.Framework.IValue>>.MoveNext() + 0x104 bytes
System.Core.dll!System.Linq.Buffer<System.Collections.Generic.KeyValuePair<Unify.Product.IdentityBroker.AdapterEntityValueCollectionKey,Unify.Framework.IValue>>.Buffer(System.Collections.Generic.IEnumerable<System.Collections.Generic.KeyValuePair<Unify.Product.IdentityBroker.AdapterEntityValueCollectionKey,Unify.Framework.IValue>> source) + 0x24b bytes
System.Core.dll!System.Linq.Enumerable.ToArray<System.Collections.Generic.KeyValuePair<Unify.Product.IdentityBroker.AdapterEntityValueCollectionKey,Unify.Framework.IValue>>(System.Collections.Generic.IEnumerable<System.Collections.Generic.KeyValuePair<Unify.Product.IdentityBroker.AdapterEntityValueCollectionKey,Unify.Framework.IValue>> source) + 0x67 bytes
Unify.IdentityBroker.Adapter.LDIF.dll!Unify.Product.IdentityBroker.LDIFToAdapterEntitySaveChangeAdapter.GetConvertedValuesFromSchema(string objectClass, System.Collections.Generic.IEnumerable<System.Collections.Generic.KeyValuePair<string,string>> values) Line 153 + 0xda bytes C#
Unify.IdentityBroker.Adapter.LDIF.dll!Unify.Product.IdentityBroker.LDIFToAdapterEntitySaveChangeAdapter.Transform(System.IO.Stream sourceValue) Line 120 + 0x4c bytes C#
Unify.IdentityBroker.Adapter.Remoting.dll!Unify.Product.IdentityBroker.LDIFAdapterBase.ExportChanges(Unify.Product.IdentityBroker.ExportedLDIFForAdapter exportedLdifForAdapter) Line 244 + 0xbe6 bytes C#
Source value in this case is a single entry: CN=Administrator,DC=UNIFY2010DEMO. The object attempting a cast is a MultiValue<StringValue> as parsed by the LDIF handling.
Adding entities with duplicate keys not handled gracefully
Adding two entities with different DNs but the same key is currently being reported as successful by the LDAP engine but is silently failing change detection, meaning that neither entity is actually committed to the connector, and no alert is displayed to the user.
If entities with duplicate keys accumulate in the change report, it might be possible to detect this and report failure on the LDAP response, avoid corruption of the connector space by committing only the entities already reported as successful, and displaying an alert to the user. This might also be an opportunity to implement user-cancellable warnings.
If the duplicate keys occur between a newly added entity and an existing entity and the DNs are different, this should be handled by rejecting the add request.
Disabled Adapters should return false on Changes Available
Disabled Adapters should return false on Changes available, with correct alerts on disabling Relational/Base connectors (and corresponding clearing alerts on enabling the adapter).
This is to prevent the FIM or potentially/alternatively EB logs from being flooded with resultant messages about the target adapters being disabled.
This would put the requirement on the user to be aware of the state of IDB with regards to Adapter enablement - the justification for this being that only explicit/manual changes to IdentityBroker components can disable adapters, which means that the user who should care about the adapter being disabled has already been a part of the domain of IdentityBroker in the first place.
An attempt to call FirstOrDefault on an empty entity repository using a field name results in a System.InvalidOperationException exception.
The following test:
[Test]
public void FirstOrDefaultWithNoDataTest()
{
using (var entityContext = CreateAndPrepareContext(PartitionId))
{
var firstItem = entityContext.Entities.FirstOrDefault(item => item.GetValueOrDefault<StringValue>(CreateEntityKey("NotThere")) == "Hello");
Assert.IsNull(firstItem);
}
}
fails with the following exception:
System.InvalidOperationException : Sequence contains no elements
This fault should be corrected, and the above unit test included in the KnownEntityRepositoryTestFixtureBase test fixture.
Identity Broker Full Import Scheduling
Hi Guys,
I've run accross an interesting issue with identity broker import scheduling. As an example, I have the following full import schedule configured for the DET Oneschool connector in SPOT:
<getAllEntities>
<timing name="Daily" offset="06:00:00" UseLocal="True" />
</getAllEntities>
The issue we are seeing, is that with this config, whenever the service is started a full import is immeadiately kicked off on this connector, regardless of the time of day. If the service is stopped and started again the same day, the import runs again.
I have seen the same behaviour on the WCIS connector with this config:
<getAllEntities>
<timing name="Daily" offset="05:30:00" UseLocal="True" />
</getAllEntities>
However for the imports that are scheduled to run at after hours in the evening, this behaviour is not exhibited. For example, the following config is on the HRuI connector:
<getAllEntities>
<timing name="Daily" offset="18:00:00" UseLocal="True" />
</getAllEntities>
It appears that any runs that are scheduled for the morning, reoccur whenever the service is started. As the Oneschool connector contains ~600k entities, this is rather inconvenient.
I've attached the entire connector config if needed for analysis. Is there anything evidently wrong here that can be quickly corrected? Is this a known issue?
Cheers
Richard
Improve feedback on inaccessible extensibility directory
When the extensibility directory cannot be written to due to permissions, the following is logged:
Application: Unify.Service.Connect.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException Stack: at Unify.Product.IdentityBroker.IdentityBrokerEngine.Dispose() at Unify.Framework.DisposeVisit.DisposeVisitMethod[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.__Canon) at Unify.Framework.Visitor.Visit[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable`1<System.__Canon>, System.Action`2<System.__Canon,Int32>) at Unify.Framework.UnifyEngine`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Dispose() at Unify.Service.IdentityBrokerService.Dispose(Boolean) at System.ComponentModel.Component.Dispose() at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase[]) at Unify.Service.ConnectServiceBootStrap.Main()
This does not really explain what's actually happening, and should be updated to reflect the exact cause for why the service couldn't start.
Customer support service by UserEcho
