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.
Incorrect severity for failing connector import job.
The following was logged when manually attempting to break a connector import job during a regression test for 3.0.7 RC:
20120126,23:13:29,Change detection engine import all items failed.,Change detection engine,Warning,"Change detection engine import all items for connector OneSchool failed with reason Cannot open database ""IAMOneSchool"" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM'.. Duration: 00:00:00.0785157 Error details: System.Data.SqlClient.SqlException: Cannot open database ""IAMOneSchool"" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM'. at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) at Unify.Framework.AdoNetDataControl.ExecuteDataSetQuery(DataSet resultSet, String commandText, IEnumerable`1 parameters, String[] tableNames, CommandType commandType) in S:\hg\Framework\Core\Master-Patch2Copy'\Source\Data\Unify.Data\AdoNetDataControl.cs:line 134 at Unify.Connector.OneSchool.OneSchoolConnectorBase`1.GetCurrentServerTime() at Unify.Connector.OneSchool.OneSchoolConnectorBase`1.GetAllEntities(IStoredValueCollection storedValueState) at Unify.Framework.ConnectorToReadingConnectorBridge.GetAllEntities(IStoredValueCollection storedValueState) at Unify.Framework.EventNotifierReadingConnectorDecoratorBase`1.GetAllEntities(IStoredValueCollection storedValues) at Unify.Framework.ChangeDetectionImportAllJob.ImportAllChangeProcess() at Unify.Framework.ChangeDetectionImportAllJob.RunBase() at Unify.Framework.MutexJobDecorator.Run() at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run() at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal
This really should be an Error, not a Warning severity type.
Log writers not functioning
Some time ago the log writers stopped functioning.
Please correct this behaviour.
Investigate delta add behaviour with new adapter pre-populate functionality
Investigate delta add behaviour with new adapter pre-populate functionality.
From CSODBB-113, it was highlighted that delta adds are a result of the entity not being present in the adapter context. (See Adapter.ProcessAttributeChangePage).
Please investigate the impact of the new processing model of pre-populating the adapter context, and come up with the possible options to work around this issue.
Thanks.
Split connector polling import
As some connectors don't only retrieve the keys that have changed, but actually retrieve the entities that have changed, the polling import interface should be split to allow for either returning the keys or the entities.
Possibly create a new return type that can be a container for either the keys or entities, and make the determination of what to do in the calling code.
Expose remove transformation
The remove transformation could be exposed as one that can be added to a transformation chain.
Could be useful where the field is required for calculations in a transformation chain, but is not required output for the export.
An example that has been given is huge group management where multiple groups are concatenated, and would cause the import to be three times the size, thus taking a lot longer to process by the identity management platform.
Do not allow the base connector key(s) to be removed.
Updating connector comment replaces the description on the display form
When you update the connector comment, the display instead shows the description has been updated, and the comment still reads that a comment has not been configured.
Cannot modify existing connector schema fields
When modifying a connector, existing connector schema fields are no longer updateable on the UI. It may be that the icons are just not visible.
Add delete confirmations on UI
Operations that could cause harm should have a confirmation prompt, much like EB did.
For example:
- Clear connector.
- Delete anything.
Confirm behaviour of Identity Broker Changes EB3 operation
Confirm that the ChangesAvailable interface performs as expected and will work correctly with the current version of Event Broker 3.
Scheduler not functioning correctly
Currently the scheduler that is used for most operations is not the one that is controlled by the user. This needs to be corrected so that the scheduler is of any use.
Also, please check how Event Broker notified the user that the scheduler is disabled, if at all. I imagine we didn't allow things to be triggered if the scheduler was stopped.
Customer support service by UserEcho
