Bug 39918 – make single sign on possible with docker containers

Bug 39918 - make single sign on possible with docker containers


Summary:	make single sign on possible with docker containers

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Docker
Version:	UCS 4.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:	38344 39473
Blocks:
	Show dependency tree / graph

Reported:	2015-11-12 15:50 CET by Florian Best
Modified:	2019-01-03 07:18 CET (History)
CC List:	4 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 Florian Best

2015-11-12 15:50:36 CET

It should be possible to make a single sign on into a UMC which runs in a docker container.

+++ This bug was initially created as a clone of Bug #39473 +++

This has to be done for the SAML cookies as well.

+++ This bug was initially created as a clone of Bug #38344 +++

... this is a feature which is needed in the docker environment as different instances are accessed via the same IP address and different ports. This is currently not possible, as one single session cookie is stored for a whole domain.

Comment 1 Alexander Kläser

2015-11-12 16:12:42 CET

From Bug 39473:
> * It is _not_ possible to use SAML for logging into the container UMC. The 
>   container has no DNS record and its FQDN can thus not be resolved. It would be
>   possible, however, if the IdP would respect the initial port for the redirect.

Comment 2 Stefan Gohmann

2019-01-03 07:18:01 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.