Postrequisites
Deprecation
As we've updated the version number and removed deprecated code, custom libraries must be recompiled using the latest Omada libraries. Once you have upgraded Omada, you must redeploy your custom files.
Below, you can find a list of deprecated and removed features in Omada Identity.
Features marked as deprecated are still available in the release in which they are deprecated. This 12-month notice period is designed to allow for the transition to new features. When we mark a feature as deprecated, it means:
- The feature is in maintenance mode only. We'll make no new changes, including changes related to interoperability with new features.
- For new customization and development work, we don't recommend using deprecated features.
Deprecated features
The following features are deprecated with the introduction of the Omada Identity 15.0.0 and will be removed on an update after 12 months:
-
CIAM
- Portal
- Feature Package
- OData Endpoints
-
MIM support
- Management Agents for ES and RoPE
- MIM related WebService Endpoints
- MIM configuration in ES
-
Process template SLAs
- Service Level Agreement wizard
- Setup Phases
- Service Dimension
- Service Rules
- Service Level Agreement wizard
-
Web page help contexts
-
Some ASPX pages
- OIM_AccessDataUpload.aspx
- OIM_AccessDataUploadHandler.aspx
- OIM_PasswordReset1.aspx
- OIM_PasswordReset2.aspx
- OIM_PasswordReset3.aspx
- My Tasks (workitemlst.aspx)
-
Process templates
- Evaluate violation process template – replaced by the Evaluate identity violation process
- Transfer identity – replaced by the Transfer Identity Assignments process
-
Process templates
- Evaluate violation process template – replaced by the Evaluate identity violation process in Omada Identity v14 update 8
- Transfer identity – replaced by the Transfer Identity Assignments process in Omada Identity v14 update 7
-
UI
- Old menu system
-
Customer Setting
- DataObject reads (Logreadhistory)
-
Command line tools:
- DataExchange.exe
- EventManager.exe
- SafeMakeDB.exe
- UserGroupManager.exe
- SAMLTokenChecker.exe
- ScreenshotGrabberTool.exe
- MigrateXMLViolationData.exe
- MigrateResourceAssignments.exe
-
API
- PasswordFilterDelegate in the PasswordFilter web service method
- Omada Identity Graph API v1 – v2.2. We only support v2.3 onwards.
- Custom authentication modules (Omada.OE.WebLib.Authentication)
- DataObjectCounterController and related classes
- Code marked as ObsoletedInVersion14
The following features are removed with the introduction of the Omada Identity 15.0.0:
- RoPE tblServiceEvent
- VBScript CodeMethods - Omada.OE.UtilityCodeAssembly.VBScript and Omada.OE.Solution.OIM.Assembly.CallVBScrip
- Password Reset Service
- Deprovisioning assignments pending in SoD
- Code marked as ObsoletedInVersion12
The following features are legacy. There are no current plans to remove them. However, these features will not receive any new features:
- Basic authentication
- Data Exchange
- OISIT
- Formparts
- WebForms (aspx) & WebServices (asmx)
- Support of Windows registry for storing configuration (encryption key, connection string)
Deprecated components
After installing the software, run the SystemInfo.sql script in the ES database.
This script is located in the Omada Identity installation folder at C:\ProgramFiles\Omada Identity Suite\Enterprise Server\Sql scripts.
This script creates a stored procedure (spSystemDiagnostics) that produces information about the Omada Identity system that is usable for diagnostics and bug investigation. The stored procedure should be executed with text output.
The script can, for example, detect the use of deprecated components that require special attention when upgrading, including:
- Use of deprecated access modifiers.
- Use of deprecated code methods.
- Other issues that should be handled if reported (for example, issues related to data objects with mandatory fields that have empty values).
Deployment of reports
After any upgrade, you need to redeploy all the standard reports.