openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-11-03T12:40:58ZopenSUSE Project Management Tool
Redmine invisAD-setup - action #43313 (Closed): Create an upgrade path from samba 4.6 to 4.7 with MIT ker...https://progress.opensuse.org/issues/433132018-11-03T12:40:58Zflaccostefan@invis-server.org
<p>We have to do upgrade tests with our heimdal based samba 4.6 setups to samba 4.7 with MT kerberos</p>
invisAD-setup - action #39161 (Closed): Build a new invisAD-setup Version 13.5https://progress.opensuse.org/issues/391612018-08-05T10:29:18Zflaccostefan@invis-server.org
<p>13.5 is a kind of intermediate version to prepare an upgrade to upcoming leap15 based Versions.</p>
<ul>
<li>This Version uses PHP7 and corNAz is already integrated in our invis-Portal.</li>
<li>It should support PHP7 based Kopano 8.6 packages and ownCloud 10.</li>
</ul>
invisAD-setup - action #36514 (Closed): ntp was removed from minimal server based setuphttps://progress.opensuse.org/issues/365142018-05-24T21:07:57Zflaccostefan@invis-server.org
<p>We have to add it to our setup (first test was negative, ntpd didn't start. Error was: blocking_getaddrinfo can not queue response / <a href="https://lists.opensuse.org/opensuse-factory/2017-06/msg00774.html" class="external">https://lists.opensuse.org/opensuse-factory/2017-06/msg00774.html</a>) or he have to check if it is possible to substitute ntpd with systemd functions or ntpsec.</p>
invisAD-setup - action #36249 (Closed): Realization of headless server-side owncloud synchronizationhttps://progress.opensuse.org/issues/362492018-05-16T06:34:58Zflaccostefan@invis-server.org
<p>We should create a script based system to synchronize some users owncloud stores from owncloud to invis server shares.</p>
<p>For example: We use the invis-server in combination with small simple fileservers. In theses cases the invis server runs at the headquarter of an organization and the simple file-servers in subsidiaries of the organization. My job is to realize a background data synchronization between headquarter an subsidiary.</p>
invisAD-setup - action #36115 (Resolved): Password-Handling during sine2 runhttps://progress.opensuse.org/issues/361152018-05-13T09:55:24Zflaccostefan@invis-server.org
<p>We should create all passwords by random pw-generator and put them in to a new setup datafile. => /var/lib/sine/invis_pws. This file should only accessible for root. </p>
<p>Showing this file could be done with "sine2 showpws".</p>
<p>Exception: This will not work for the CA private-key password. </p>
invisAD-setup - action #36108 (Resolved): Connect kimai to ADhttps://progress.opensuse.org/issues/361082018-05-12T12:23:35Zflaccostefan@invis-server.org
<p>sine2 should prepare the connection of kimai to the activedirectory</p>
invisAD-setup - action #36106 (Resolved): Implentation of invoiceplane to invis-server Setuphttps://progress.opensuse.org/issues/361062018-05-12T12:18:17Zflaccostefan@invis-server.org
<p>Implementation of the opensource invoiceplaning Software to invis-Server</p>
invisAD-setup - action #36079 (Closed): Modify sine2 / invisAD-setup to be compatible with leap 15https://progress.opensuse.org/issues/360792018-05-10T18:59:10Zflaccostefan@invis-server.orginvisAD-setup - action #36003 (Resolved): Switch to dehydrated package from distributionhttps://progress.opensuse.org/issues/360032018-05-08T12:17:56Zflaccostefan@invis-server.org
<p>The let's encrypt client dehydrated is now part of the opensuse leap 15 standard repos. We should switch to this package, instead of building our own package.</p>
invisAD-setup - action #35946 (Rejected): GroupPolicies to rollout software to windows-clientshttps://progress.opensuse.org/issues/359462018-05-06T11:58:51Zflaccostefan@invis-server.org
<p>We should add GPOs to the invis-Server AD for an automatic rollout software-packages like Kopano-Outlook-Extension, Kopano-Deskapp or ownCloud-Client to the connected windows clients</p>
invisAD-setup - action #35943 (Closed): Switch from networkmanager back to wickeddhttps://progress.opensuse.org/issues/359432018-05-06T10:42:15Zflaccostefan@invis-server.org
<p>It seems that even inside es minimal server setup of opensuse leap 15 the network-management is done with networkmanager. We should switch back to wickedd. This could be done inside our netsetup-Script.</p>
invisAD-setup - action #33736 (Closed): Renewing the Kopano configuration fileshttps://progress.opensuse.org/issues/337362018-03-23T15:10:44Zflaccostefan@invis-server.org
<p>This should be done in two steps.</p>
<p>First step is to put our individual settings of the existing files to the new example files of Kopano 8.5.x</p>
<p>This step includes Ticket <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="action: PFS Setup for Kopano (Closed)" href="https://progress.opensuse.org/issues/27094">#27094</a>.</p>
<p>Second step is to switch to the new kopano LDAP schema and then create a new ldap.cfg. With kopano 8.5.x the ldap.cfg is splitted in two parts. Part one is in /etc/kopano. Inside this file the second part (/usr/share/kopano/ldap.active-directory.cfg) is included.</p>
<p>...and we have to think about how to migrate from the old zarafa-schema to the new kopano-schema.</p>
invisAD-setup - action #30592 (Closed): Dokuwiki Module is brokenhttps://progress.opensuse.org/issues/305922018-01-21T09:42:14Zflaccostefan@invis-server.org
<p>The Dokuwiki sine2 module is broken caused by an no longer existing download link for the display-wikipage plugin. This plugin isn't maintained for over 2 years now, it was necessary for the monobook template. We should switch to a more modern template. </p>
invisAD-setup - action #29886 (Closed): Building all keypairs inside the sine2 sysprep modulehttps://progress.opensuse.org/issues/298862017-12-30T11:42:58Zflaccostefan@invis-server.org
<p>All keys and certs should be build during the run of the sysprep modul, because builing keys needs user interaction which interrupts the sine2 run.</p>
invisAD-setup - action #25532 (Closed): Combine z-push and owncloud vHostshttps://progress.opensuse.org/issues/255322017-09-23T15:40:15Zflaccostefan@invis-server.org
<p>A lot of possible recipients of an owncloud share-link are behind of a proxy server. The most proxy servers block the access to ports different from the standard http(s) ports 80 and 443.</p>