Azure Application Proxy
Comments
-
We would like to secure outside access to any Decisions form we want to host on external-facing websites and only allow portal access to selected users on our internal network. Do you guys have documentation about how to deploy this and what practices to follow?
Our concern is that our Decisions instance has access to highly sensitive data (which is required due to some of our workflows), and we want to avoid being one misconfiguration or vulnerability away from leaking data.
-
[url=https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-proxy]Azure Application Proxy[/url][font=Roboto, Arial, Helvetica, sans-serif] will work with your Production server if it is [/font][url=https://documentation.decisions.com/docs/integrating-active-directory-with-decisions]integrated with Active Directory[/url][font=Roboto, Arial, Helvetica, sans-serif]. Alternatively, there is a Boolean property for Decisions accounts named Can Use Portal which can be modified via flow so that only one group, a set of groups, or a set of hand-picked accounts could enter the portal. Ive attached an example of how to set this up in Decisions.[/font]
Howdy, Stranger!
Categories
- 2.1K All Categories
- 18 General
- 155 Installation / Setup
- 991 Flows
- 86 Rules
- 203 Administration
- 204 Portal
- 433 General Q & A
- 600 Forms
- 282 Reports
- 3 Designer Extensions
- 38 Example Flows
- 32 CSS Examples
- 1 Diagram Tile
- 5 Javascript Controls
- 139 Pages
- 1 Process Mining
- New Features
- 150 Datastructures
- 50 Repository
- 169 Integrations
- 25 Multi-Tenant
- 21 SDK
- 40 Modules
- 38 Settings
- 20 Active Directory
- 12 Version 7
- 34 Version 8