Showing 221 - 230 of 255 results
-
https://docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-security/system-security-getUserRolesFetches the roles for a user from the Gateway.
-
https://docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-security/system-security-getUsernameReturns the currently logged-in username.
-
https://docs.inductiveautomation.com/docs/7.9/appendix/scripting-functions/system-security/system-security-lockScreenUsed to put a running client in lock-screen mode.
-
https://docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-security/system-security-switchUserAttempts to switch the current user on the fly.
-
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/ignition-modules/vision/security-in-vision/security-in-scriptingWhile the Vision system has many options for securing individual components and clients, it is possible to have requirements that go further than the options that are available. With scripting, you can create any type of security that you may need. This is mainly done through the use of the system.security.getRoles
-
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/7.9/security/user-sourcesUser Sources
-
https://docs.inductiveautomation.com/docs/7.9/security/using-audit-profilesAudit Profiles cause Ignition to record details about specific events that occurred. Audit Profiles are simple to set-up, and immediately start to record events. By default, only Tag writes, SQL UPDATE, SQL INSERT, and SQL DELETE statements are recorded. This allows you to keep track of which user wrote
Were these results helpful?