openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-02-20T07:36:54ZopenSUSE Project Management Tool
Redmine invisAD-setup - action #63634 (New): We should publish a list with the expiry dates of all VPN cl...https://progress.opensuse.org/issues/636342020-02-20T07:36:54Zflaccostefan@invis-server.org
<p>The VPN client certs we create have a 24 month time to live. Actually the users have no information about this, the don't know when there clients certs epxire. More than once this caused problems in practice.</p>
invisAD-setup - action #63631 (Closed): We should publish the CRL expiration date via invis portalhttps://progress.opensuse.org/issues/636312020-02-20T07:32:14Zflaccostefan@invis-server.org
<p>Our CRL (Certification Revocation List) expires 6 month after creation. We should publish this date via invis-Portal.</p>
invisAD-setup - action #54389 (New): DNS-Updates via DHCP-Server should be possiblehttps://progress.opensuse.org/issues/543892019-07-18T06:37:55Zflaccostefan@invis-server.org
<p>In our setup every try to update DNS-Records dynamically fails:</p>
<p>Unable to add forward map from LANCOM_884_VOIP.baettenhausen.local to 192.168.1.205: REFUSED</p>
<p>This should be possible.</p>
<p>How to setup: <a href="https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Setting_up_BIND" class="external">https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Setting_up_BIND</a></p>
invisAD-setup - action #52019 (Closed): invis-Portal: Add a new function-sitehttps://progress.opensuse.org/issues/520192019-05-27T08:25:26Zflaccostefan@invis-server.org
<p>It should be possible to execute some administrative shell-scripts via invis-portal.</p>
invisAD-setup - action #51920 (Closed): invis-Server Setup Test with openSUSE Leap 15.1https://progress.opensuse.org/issues/519202019-05-23T10:05:12Zflaccostefan@invis-server.org
<p>We should build invis-Server 14.1 on base of Leap 15.1</p>
invisAD-setup - action #51386 (Closed): invis-Server should be compatile with Btrfs.https://progress.opensuse.org/issues/513862019-05-12T07:25:07Zflaccostefan@invis-server.org
<p>First testinstallation with Btrfs on the Root-Volume shows that it was impossible to boot the server after setup with sine2.</p>
invisAD-setup - action #51383 (Closed): invis-Portal: Filter for Hostlisthttps://progress.opensuse.org/issues/513832019-05-12T07:21:37Zflaccostefan@invis-server.org
<p>It should be possible to filter the elements of the hostlist by type like we do it in the userlist.</p>
invis-sub-setup - action #46718 (In Progress): Create a setup-script for invis-sub-serverhttps://progress.opensuse.org/issues/467182019-01-26T15:49:46Zflaccostefan@invis-server.org
<p>Major steps to realize with this Script:</p>
<ol>
<li>Establish an openVPN connection to the main invis-server</li>
<li>Join the Domain as a "Read Only Domain Controller" (RODC)</li>
<li>Setup sssd</li>
<li>Setup local samba shares</li>
<li>realize (owncloud based) data synchronization between sub and main-server</li>
</ol>
<p>Some of these steps are already realized inside the joininvis-script from the invisAD-client package.</p>
<p>Joining the domain as a rodc (<a href="https://de.wikipedia.org/wiki/Read_Only_Domain_Controller" class="external">https://de.wikipedia.org/wiki/Read_Only_Domain_Controller</a>) instead of a simple member server seems to be the better way. In a productive environment at one of our custumers I tried to realize a subsidiary server as a simple member-server. Nearly every time the vpn-connection caused by a not very stable internet-connection, I had to rejoin the domain with the sub-server to give the sub-users access to their local samba-shares. </p>
invisAD-setup - action #37414 (In Progress): Implementation of SingleSignOnhttps://progress.opensuse.org/issues/374142018-06-15T07:57:23Zflaccostefan@invis-server.org
<p>Step by step we should implement SSO for as much applications as possible. First step would be to fit the apache2 setup for SSO.</p>
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 #29909 (Closed): Upgrade to PHP7https://progress.opensuse.org/issues/299092018-01-02T09:29:18Zflaccostefan@invis-server.org
<p>We have to upgrade the invis-server to php7. The now used Version 5.5. is out of maintenance and newer openSUSE Versions possibly ship only php7.</p>
<p>I think that the most wepapps we have included in invis-server still support php7. Biggest problem could be the invis-portal.</p>
invisAD-setup - action #27090 (Resolved): ldb library conflicthttps://progress.opensuse.org/issues/270902017-10-28T09:08:44Zflaccostefan@invis-server.org
<p>Since one of the last upgrades of the package ldb to version 1.2.x in our samba AD repos, sssd refuces to start after setup. After installing the original openSUSE 42.3 package ldb in version 1.1.29 everything works.</p>
<p>The problem is that our own samba packages are build against the newer ldb package.</p>
<p>I've no idea how we can fix this. Just installing the older package couldn't be the right way, this may cause other dependency problems.</p>
invisAD-setup - action #25198 (Rejected): invis-Server Upgrade Systemhttps://progress.opensuse.org/issues/251982017-09-12T05:53:59Zflaccostefan@invis-server.org
<p>We should build an upgrade System or Script for invis-Server to support minor-release jumps.</p>
<p>Such a system has to do only the projectable things like adding new stuff (schema addons, data) to Active-Directory or setting new Versionnumbers. To do the whole upgrades automatically is impossible in my opinion. </p>
<p>Any suggestions to this topic?</p>
invis-server - action #24736 (Closed): Repositories are brokenhttps://progress.opensuse.org/issues/247362017-09-07T10:06:51Zflaccostefan@invis-server.org
<p>If I do a zypper ref on invis-servers I get the following answer from zypper:</p>
<p>Metadaten von Repository 'Common packages for invis-Server stable & unstable (openSUSE_42.2)' abrufen --------------------------------------[/]<br>
Datei './repodata/a710cf170ceff2acfcccc3bc4919f44d06ce7246231c684c587dced0ed348855-primary.xml.gz' auf Medium '<a href="http://download.opensuse.org/repositories/spins:/invis:/common/openSUSE_Leap_42.2/" class="external">http://download.opensuse.org/repositories/spins:/invis:/common/openSUSE_Leap_42.2/</a>' nicht gefunden</p>
<p>Abbrechen, wiederholen, ignorieren? <a href="a" class="external">a/w/i/...? zeigt alle Optionen</a>:</p>
<p>This happens with all our repos. </p>
invis-backup - action #23794 (Rejected): Implementing rdiff-backup-web to invis-serverhttps://progress.opensuse.org/issues/237942017-08-30T18:53:30Zflaccostefan@invis-server.org
<p>The invis-server own backup-solution "invis-rdbu" uses rdiff-backup as the main backup-tool. </p>
<p>Restoring Data from a rdiff-backup repository isn't easy enough to give our users the oportunity to restore data from the backup by themself. Implemting the fuse-based rdiff-backup Filesystem in combination with rdiff-backup-web makes it much more easy to do this job. </p>
<p>Ingo has allready build a rdiff-backup-fs package in our OBS Repos, no we can start implementing and testing rdiff-backup-web.</p>
<p>rdiff-backup-web on Sourceforge: <a href="http://rdiffbackupweb.sourceforge.net/" class="external">http://rdiffbackupweb.sourceforge.net/</a></p>
<p>Caution: This software is in an early alpha state, perhaps it isn't stabel enough for our needs. </p>