Identity Connect should allow an Administrator to upload a keytab file, a css file, and a png file to customize the Identity Connect experience.
This story describes the functional requirements needed to support uploading custom files to the Identity Connect instance. Out of the box, v2.1 of the bridge supports uploading files to security/identityConnect.HTTP.keytab, ui/extension/css/custom.css, and ui/extension/images/logo.png and the new Identity Connect will need to match this support.
Create a service that accepts file content and will replace the content of a file on the host system with the submitted content. The file to update on the host system should be specified within config. Each file that supports upload should be specified in separate configs.
There should be no designated UI for this. The UI will incorporate the calls to the service within the settings page.
1. Upload a keytab file to security/identityConnect.HTTP.keytab
2. Upload a css file to ui/extension/css/custom.css
3. Upload a png file to ui/extension/images/logo.png
Non Functional Requirements
The service should leverage CREST-108 as determined by