Modelling - External requests phase 3

[tpurschke]

@tpurschke

• customer decision: how to deal with duplicate network object names (fails at least when they are used within the same rule)
  • prevent duplicates (db constraint, ui check)
  • artificially add uniqueness to name
  • leave it to users to prevent duplicate names
• test performance: how long does the analysis phase take when we have 50 connections and 50 ARs?
• to clarify: bundling of access requests also for same connection on different managements? Ask Tufin support. Solution probably: create one access request per management using the objects of the respective management.

@abarz722

• order of tasks is non-deterministic after requesting a change (e.g. 4,5,6,7,1,2,3,8)
• Re-Init ticket hangs in spinner (but seems to work anyway)
• Error message mouse-over tooltip sometimes only contains "ExtRejected:" but not the message itself
• Test basic functionality via FWO API: modify AR (add new app server), initiate requesting this change via SC (probably not possible yet)
  • input: internal ticket create API call
  • output: SC API call which modifies AR
• also handle access requests which contain host objects instead of groups
• if objects (e.g. NAs) do not exist any more - set connection status to "incomplete"
• Plan app-server change handling: Name change vs. IP change - how can an app server move from manually added to being imported?
• try to break down tickets per changed connection to enable requesting additional changes for the same app
• display SC ticket status - display the actual ticket step
• still got a timing issue (imports only once a day) when someone only modifies groups and makes two of these changes on the same day, current customer prod import time: 10 min; also relevant when we allow AR changes via API; remediation: increase import frequency (loop with 40s pause only?)
• also request ip ranges