What's new in 11​.2​.1

New features in OSM Administration

These features are new in AVEVA™ Operational Safety Management 11.2.1.

Sign in to OSM Admin now uses Windows AD credentials

OSM Administration has switched to using Active Directory authentication. With the exception of OSM user account cowapp, regular users can no longer sign in to Admin with an OSM user account.

Users must now use AD credentials including domain name to sign in to OSM Administration.

A Windows domain authentication will be validated against Windows / Active Directory.

• domain\user.name

• domain password

OSM user accounts will still exist, but no longer have a password function. All password functionality has been removed.

Important: An OSM user account must still exist for each user. The OSM user name and Windows Credentials name must match.

AVEVA™ Identity Manager for client authentication

Operational Safety Management now uses AVEVA™ Identity Manager for client authentication. It requires a user to enter Windows credentials. In response to cybersecurity issues in today's networked world, it was necessary to integrate an identity manager.

• It's no longer possible to enter an e-mail address for client authentication.

• OSM URL for single sign-on is no longer supported.

  Specify Administrator email addresses

When OSM needs to send an email to administrators of OSM, there is a new setting to add email addresses, so that warnings regarding configuration errors are sent to administrators. You can configure email addresses with the cowApplicationAdministratorEmail application setting.

• The setting can contain one or several email addresses.

• Each address is separated by a semi-colon (;).

We recommend that you use this setting to send configuration error messages to administrators only.

New version of OSM Admin Password

To change the password for DB account cow_user, you must use the latest version of OSM Admin Password software utility.

Maximum number of periods

There is a new maximum limit value on number of periods that a work permit is valid for. The maximum number is independent from the default number of periods. For example, the default number may be 7 periods, but the maximum number is 14 periods. See Set number of activation periods.

Not able to scan work permits printed before OSM 11.2.1

It will not be possible to scan work permits that were printed before OSM is upgraded to 11.2.1. You will need to reprint old work permits so they will scan properly. This also applies for isolation point labels.

Support for Portuguese-Brazilian

We have added Portuguese-Brazilian as a supported language.

Deprecated features in OSM Administration

Functionality is marked as deprecated when a feature is still supported in the current release, but might be removed in a future release. We advise that you phase these features out of your projects and begin to use alternative features.

• User Groups - The Access groups category on the System Administration menu has been deprecated. This will be replaced in the future by a new user management system.

  Discontinued features in OSM Administration

Discontinued features have been removed from the product, or are no longer supported.

• Operational Safety Management no longer supports HTTP protocol. Using secure HTTPS protocol is now a requirement.

• OSM URL for single sign-on is no longer supported.

  Changes to installation requirements

There are the following changes to installation requirements.

• HTTPS - Operational Safety Management now requires using secure HTTPS protocol.

• Need new license to upgrade - A new license is not usually needed for an upgrade. However, for 11.2.1 only, you will need to have a new license.

• PCS Server installation - It is now possible to have one PCS Server for multiple web client installations. For example, webclientprod and webclientuat.

• New client types for PCS - In addition to web client, there are two new client types: mobile client and APIAdapter client.

  Security updates

We made the following security updates.

• Active Directory authentication for login to OSM Administration.

• Using secure HTTPS protocol is now a requirement.