Users and Roles

On the Identity Providers screen you can test a username and password combination against an Identity Provider (IdP).

Tag security is often the best way to configure security for data access. By defining security on a tag, you affect the tag across wherever it is used, as opposed to configuring component security on each component that displays or controls that tag.

This section provides an example of how to connect an Identity Provider that is using the SAML protocol. This example uses the Okta IdP service. Your IdP vendor may differ and the specific links will differ.

The User Attribute Mapping page allows you to map information in the Identity Providers (IdP) response document to easily understandable properties. These properties are then made available as Session Properties in the Perspective Session. To work, this requires that the Gateway already has a valid IdP

You can verify that a user exists in a given User Source, if the password is correct, what roles a user has, and any other information added about the user.

This section provides an example of how to connect an Identity Provider that is using the OpenID Connect 1.0 protocol. This example uses the Okta IdP service. Your IdP vendor may differ and the specific links will differ.

You can force an operator to enter a personal identification number (PIN) in order to hear a Voice alarm notification message. It’s a good idea to validate that the person who is receiving the voice alarm is the correct person by requiring a PIN.

This page details various networking and security settings you may need to configure for your Cloud Edition virtual machine.

This page details various networking and security settings you may need to configure for your Cloud Edition EC2 instance.