-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
Currently the auth mechanism for the interactive workflow was disabled, so the AS API was freely accessible. We should re-enable it using the same approach already adopted for the automatic workflow.
Open question
- Currently the ISO is generated in a generic way and it doesn't contain any specific customer bit. How to address it?
- Would it be acceptable to use a generic token (given the disconnected installation point of view)?