Bug 51639 – Feature Request: Seperate App IAM integration from App software installation

Bug 51639 - Feature Request: Seperate App IAM integration from App software installation


Summary:	Feature Request: Seperate App IAM integration from App software installation

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	App Center
Version:	UCS 4.4
Hardware:	Other Windows NT

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	App Center maintainers
QA Contact:	App Center maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2020-07-08 08:05 CEST by Michael Grandjean
Modified:	2020-07-08 09:10 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Grandjean

2020-07-08 08:05:59 CEST

I want to be able to only use the IAM integration of Apps, but not install the App software packages (or docker container) itself.

Scenarios: 
a) I use UCS as IAM and want to deploy a larger installation of {Nextcloud,ownCloud,Open-Xchange,Kopano,Relution,...} distributed across several servers. Those servers might not be UCS systems.
b) I introduce UCS as new IAM and have existing installations of {Nextcloud,ownCloud,Relution,...} that I want to connect to UCS

In both cases it would be great if there's a simple option to just install e.g. the LDAP schema extension and the extended attributes without also having to install the application itself on UCS.

Comment 1 Ingo Steuwer

2020-07-08 08:45:25 CEST

I'm not sure if we should try to do this in a generic way in the app center. I Think we should focus on individual usecases, like we started by providing an App for OX provisioning based on their SOAP API.