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.
Aderant Expert incorrectly handles workgroup management.
If a workgroup code is specified it will validate that the workgroup doesn't exist as opposed to confirming that it exists before continuing.
SharePoint configuration wizard should highlight fields that are marked as Choice List types
Choice List types can cause some issues in an identity management solution - see the troubleshooting information. It would therefore be helpful if the SharePoint Connector Configuration wizard could highlight fields that are marked as choice list fields (as simple as checking the ChoiceTypes enum of the attribute's PropertyInfo when retrieving the schema).
Moreover, if the choice list is marked as "Closed", the field could be marked as readonly in the schema - see http://msdn.microsoft.com/en-us/library/microsoft.office.server.userprofiles.choicetypes.aspx. This could also be done by default in order to prevent new choices from being added when the property is not set to "Open" - although this would prevent updates of the field to other valid options for the user. Some further investigation into appropriate behaviour in this case should be carried out.
Estimate includes familiarization with UI, formatting of the XSL, and testing.
Deletes in composite adapter broken
The check to confirm that a delete has succeeded has regressed Identity Broker.
In a composite adapter, entity ids don't have to belong to the adapter being visited, and as such the error will occur for every delete performed.
If the adapter containing the deleted entity is first in the configuration, the delete will succeed, but report back a failure when an exception in thrown in another adapter.
If the adapter containing the deleted entity is not the first in the configuration, the delete will fail and report back the failure.
Configuration needs to be checked in IdentityBroker for the uniqueness of adapter ids with regards to inner adapter ids
An identity broker adapter engine configuration similar to the following will not break, and will overwrite entities in the db:
<composite-adapter id="YYYYYYY">
<adapter id="XXXXXXXXX" />
</composite-adapter>
<adapter id="XXXXXXXXX" />
Clear changes table when entities not present
I have not performed any operations on my local IdB 4 build, but the adapter is reporting 51909 changes. This is because there are 51909 items in the changes table for the adapter. However, there are no entities present in the Entity table. Relationship should be added between the two tables to clear the changes when the entity no longer exists.
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.
Customer support service by UserEcho
