Apama 10.3 | Apama Documentation | Building and Using Apama Dashboards | Dashboard Deployment | Administering Dashboard Security
Administering Dashboard Security
Administering authentication
Authentication for local and WebSphere deployments
Administering authorization
Securing communications
Example: Implementing LoginModule
Deployed dashboards are protected by the authorization and authentication facilities provided by Apama and your application server.
Apama's dashboard authentication facility prompts users for credentials before allowing any access to deployed dashboards. It gives you the ability to customize authentication by either configuring your application server to use the security realm and authentication service of your choice or by supplying any JAAS-supported authentication module as a plug-in to the data server or display server. See Administering authentication.
Apama's authorization facility includes access control that gives you the ability to control who can use a given dashboard. The facility also gives you the ability to control who can use dashboards to gain a given type of access to a given scenario, scenario instance, DataView definition, or DataView item. And it gives the ability to control who can send events from dashboards using the Send Event command. See Administering authorization.
In addition to authenticating and authorizing users, you need to consider how you will protect data sent to dashboards. This is discussed in Securing communications.
To protect the security of personal data, see Protecting Personal Data in Apama Applications.

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.