Showing 351 - 360 of 1526 results
-
https://docs.inductiveautomation.com/docs/8.1/platform/securitySecurity options in Ignition provide many ways to safeguard access to your data and applications. You control not only who accesses your systems, but when and where they can access them. Ignition offers two authentications strategies: Classic Authentication Strategy or Identity Provider Authentication
-
https://docs.inductiveautomation.com/docs/8.1/platform/security/identity-provider-authentication-strategy/security-level-rules
-
https://docs.inductiveautomation.com/docs/8.1/ignition-modules/vision/security-in-vision/component-and-window-securityRole-based security inside of Vision works on multiple levels: component, group, container, and window levels. Each of these levels also have special categories of security that help with tuning security to various design considerations.
-
https://docs.inductiveautomation.com/docs/8.1/platform/security/identity-provider-authentication-strategy/configuring-identity-providers/user-attribute-mappingThe 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
-
https://docs.inductiveautomation.com/docs/7.9/security/user-sourcesUser Sources
-
https://docs.inductiveautomation.com/docs/7.9/opc-ua-and-device-connections/dnp/dnp3What is DNP3?
-
https://docs.inductiveautomation.com/docs/8.1/platform/designer/windows-linux-and-mac-keyboard-shortcutsUsing Keyboard Shortcuts in the Designer
-
https://docs.inductiveautomation.com/docs/8.1/system-architectures/security-architecturesNetwork Segmentation
-
https://docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-securitySecurity Functions
-
https://docs.inductiveautomation.com/docs/8.1/platform/security/classic-authentication-strategyThe Classic Authentication strategy authenticates users against a User Source. Both the Designer and Vision Client can authenticate users with this strategy.

Were these results helpful?