IRISSECURITY Upgrade Impact

Previously, when security globals were stored in the IRISSYS database, users could access security data with the following privileges:

• %DB_IRISSYS:R: Read security globals both directly and through security APIs.

• %DB_IRISSYS:RW: Read and write security globals.

• %DB_IRISSYS:RW and Admin_Secure:U: Administer security through security APIs.

Starting InterSystems IRIS 2025.2:

• Security globals are now stored in IRISSECURITY.

• Users can no longer access security globals directly.

• Both %DB_IRISSYS:R and %Admin_Secure:U are the minimum privileges needed to both access security data (through the provided security APIs) and administer security through the various security classes.

• For general security administration, you can use the new %SecurityAdministrator role.

• Read-only access to security data (previously available through %DB_IRISSYS:R) has been removed.

In InterSystems IRIS 2025.2, the following security globals have been moved from IRISSYS to the ^SECURITY global located in IRISSECURITY:

• ^SYS("SECURITY")

• ^OAuth2.*

• ^PKI.*

• ^SYS.TokenAuthD

The following table lists the most notable globals that have been moved, their security classes, old locations, and new locations:

Previously, you could map OAuth2 globals to a different database, which allowed OAuth2 configurations to be mirrored.

Starting in InterSystems IRIS 2025.2, OAuth2 globals can no longer be mapped, and IRISSECURITY cannot be mirrored. If you depended on this behavior for mirroring, you can use any of the following workarounds:

• Manually make changes to both the primary and failover.

• Export the settings from the primary and then import them to the failover (requires %All).

To export OAuth2 configuration data:

set items = $name(^|"^^:ds:IRISSECURITY"|SECURITY("OAuth2"))_".gbl"
set filename = "/home/oauth2data.gbl"
do $SYSTEM.OBJ.Export(items,filename)

To import OAuth2 configuration data:

do $SYSTEM.OBJ.Import(filename)

Previously, SQL security was controlled by the CPF parameter DBMSSecurity. When DBMSSecurity was disabled, users with SQL privileges could arbitrarily query all tables in the database.

Starting in InterSystems IRIS 2025.2:

• The DBMSSecurity CPF parameter has been replaced with the system-wide SQL security property. You can enable (1, default) or disable (0) this in several ways:

  • Management Portal: System Administration > System > System Security > System-wide Security Parameters > Enable SQL security

  • $SYSTEM.SQL.Util.SetOption()Opens in a new tab:

    do ##class(%SYSTEM.SQL.Util).SetOption("SQLSecurity", 1)
    

    

  • Security.System.Modify()Opens in a new tab:

    set properties("SQLSecurity")=1
    do ##class(Security.System).Modify(,.properties)
    

    

• Security tables can now only be queried through the Detail and List APIs, which require both %DB_IRISSYS:R and %Admin_Secure:U even when SQL security is disabled.

For example, to get a list of roles, you can no longer directly query the Security.Roles table. Instead, you should use the Security.Roles_List() query:

SELECT Name, Description FROM Security.Roles_List()

In previous versionsOpens in a new tab of InterSystems IRIS, the procedure for creating rules for managing a web application's access to additional percent classes involved writing to security globals. You can accomplish this in InterSystems IRIS 2025.2 through the Management Portal or the ^SECURITY routine.

To create a class access rule with the Management Portal:

• Go to System Administration > Security > Web Applications.

• Select your web application

• In the Percent Class Access tab, set the following options:

  • Type: Controls whether the rule applies to the application's access to just the specified percent class (AllowClass) or all classes that contain the specified prefix (AllowPrefix).

  • Class name: The percent class or prefix to give the application access to.

  • Allow access: Whether to give the application access to the specified percent class or package.

  • Add this same access to ALL applications: Whether to apply the rule for all applications.

To create a class access rule with the ^SECURITY routine:

• From the %SYS namespace, run the ^SECURITY routine:

  DO ^SECURITY
  

  

• Choose options 5, 1, 8, and 1 to enter the class access rule prompt.

• Follow the prompts, specifying the following:

  • Application?: The name of the application.

  • Allow type?: Whether the rule applies to the application's access to just the specified percent class (AllowClass) or all classes that contain the specified prefix (AllowPrefix).

  • Class or package name?: The class or prefix to give the application access to

  • Allow access?: Whether to give the application access to the specified class or package.