Manuel talks and notes #726

Closed
opened 2026-09-24 23:10:38 +00:00 by Cordy · 2 comments
Owner

so i have a small blurp as a reminder from a longer talk i had with Manuel.

[20:26, 9/24/2026] Manuel Novak: Issues:

  • AD connection strings
  • TLS für custom pki bzw. private CAs
    [20:26, 9/24/2026] Nik: deeper explanation and goals
    [20:42, 9/24/2026] Manuel Novak: Issue:
  • Skalierbarkeit, Storage, User

as well as my somewhat short summary, will need to come with follow up questions towards me to drill down on these.

so there are a total of 4 things/issues/epics that might or will result of this:

AD groups handling and how AD grants users access to Cairn.

what was described is that in a environment, is that usually Users are given access to a fileserver by being part of a certain admin group e.g. oCIS-users, or CairnUsers, and then they are even allowed login. how is this enforced in the industry? how do competitors handle this? are there any issues they encoutnered pitfalls?

AD Connection strings how an AD gets connected to Cairn

this one most likely links to the AD groups handling.

TSL custom PKI/Private CA handling within an environment.

Research Competitors on this

scalability, how are files and users handled on a deployement when Cairn scales in nombers of pods within kubernetes

Research Competitors on this

so i have a small blurp as a reminder from a longer talk i had with Manuel. [20:26, 9/24/2026] Manuel Novak: Issues: - AD connection strings - TLS für custom pki bzw. private CAs [20:26, 9/24/2026] Nik: deeper explanation and goals [20:42, 9/24/2026] Manuel Novak: Issue: - Skalierbarkeit, Storage, User as well as my somewhat short summary, will need to come with follow up questions towards me to drill down on these. so there are a total of 4 things/issues/epics that might or will result of this: ### AD groups handling and how AD grants users access to Cairn. what was described is that in a environment, is that usually Users are given access to a fileserver by being part of a certain admin group e.g. oCIS-users, or CairnUsers, and then they are even allowed login. how is this enforced in the industry? how do competitors handle this? are there any issues they encoutnered pitfalls? ### AD Connection strings how an AD gets connected to Cairn this one most likely links to the AD groups handling. ### TSL custom PKI/Private CA handling within an environment. Research Competitors on this ### scalability, how are files and users handled on a deployement when Cairn scales in nombers of pods within kubernetes Research Competitors on this
Author
Owner

hyrsh has uploaded his issues regarding this with his more thourough insight:

Initial Kubernetes deployment
#752 opened

Horizontal scalability
#742 opened

ActiveDirectory connection standard
#741

TLS Config Options for certificate handling
#740

hyrsh has uploaded his issues regarding this with his more thourough insight: Initial Kubernetes deployment #752 opened Horizontal scalability #742 opened ActiveDirectory connection standard #741 TLS Config Options for certificate handling #740
Author
Owner

Closing as agreed with Nikola (2026-10-17): every point from the talk is now its own issue, #740 (TLS), #741 (AD login group), #742 (horizontal scaling) and #752 (Kubernetes deployment).

Closing as agreed with Nikola (2026-10-17): every point from the talk is now its own issue, #740 (TLS), #741 (AD login group), #742 (horizontal scaling) and #752 (Kubernetes deployment).
Cordy closed this issue 2026-10-17 13:06:00 +00:00
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#726
No description provided.