argonaut issueshttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues2024-02-17T00:42:48Zhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5783merge dev into master for 1.42024-02-17T00:42:48Zbmortiermerge dev into master for 1.4Argonaut 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5782Update the changelog for 1.42024-02-17T00:41:31ZbmortierUpdate the changelog for 1.4Hello,
we need to update the changelog for 1.4
CheersHello,
we need to update the changelog for 1.4
CheersFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5763change the donate part to add all the crowfunding possibilities2024-02-17T00:41:31Zbmortierchange the donate part to add all the crowfunding possibilitieshello,
we need to replace the donate with all our crowfunding possibilities
Cheershello,
we need to replace the donate with all our crowfunding possibilities
Cheersbmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5777Change the text in the professional support in the README.md2024-02-17T00:41:31ZbmortierChange the text in the professional support in the README.mdHello,
to be more in line with the website we should change the text for the professional support
CheersHello,
to be more in line with the website we should change the text for the professional support
CheersArgonaut 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5779remove reference to freenode.net in2024-02-17T00:41:31Zbmortierremove reference to freenode.net inHello,
we need to remove all reference to freenode.net in the README.MEHello,
we need to remove all reference to freenode.net in the README.MEFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5776add a SECURITY.MD2024-02-17T00:41:30Zbmortieradd a SECURITY.MDHello,
we miss rhe security.md for github
CheersHello,
we miss rhe security.md for github
CheersArgonaut 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5752update de manpages for 1.4-dev2024-02-17T00:41:23Zbmortierupdate de manpages for 1.4-dev## Descriptive title for this enhancement
update de manpages for 1.4-dev
### Actual behavior
manpages are still at 1.2 version
### Expected behavior
Have the manpages refreshed with the correct version and functionalities
### Benef...## Descriptive title for this enhancement
update de manpages for 1.4-dev
### Actual behavior
manpages are still at 1.2 version
### Expected behavior
Have the manpages refreshed with the correct version and functionalities
### Benefits
current documentation
### Possible Drawbacks
nonebmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5744Add SupAnn 2018 account life cyle support in user-reminder2024-02-17T00:34:29ZbmortierAdd SupAnn 2018 account life cyle support in user-reminder## Descriptive title for this enhancement
Add SupAnn 2018 account life cyle support in user-reminder
### Actual behavior
User reminder support posix and ppolicy for the user reminder functionality
### Expected behavior
We need to s...## Descriptive title for this enhancement
Add SupAnn 2018 account life cyle support in user-reminder
### Actual behavior
User reminder support posix and ppolicy for the user reminder functionality
### Expected behavior
We need to support the SupAnn account life cyle support in user-reminder to be able to use user-reminder when we don't have any posix or ppolicy usage but we have the life cycle of the account managed on the supann entries of the users
### Step by step description of new behaviour
### Benefits
* Be able to use user-reminder in SupAnn 2018 account life Cycle
* Be able to use user-reminder when we don't have any password in federation mode and use the SupAnn account,life cyle to do that
### linked ticket
https://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/issues/5907
CheersArgonaut 1.4Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/4108Deployment - Dual Boot Windows/Linux (OPSI/FAI)2024-02-16T15:04:44ZCôme ChillietDeployment - Dual Boot Windows/Linux (OPSI/FAI)In argonaut server,
FAI and OPSI modules need to see that they are both active and manage this.
The idea would be for OPSI to go first and start the FAI installation when finished.
* Relations:
* copied_to #3479In argonaut server,
FAI and OPSI modules need to see that they are both active and manage this.
The idea would be for OPSI to go first and start the FAI installation when finished.
* Relations:
* copied_to #3479Argonaut 1.4Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5676argonaut-ldap2zone view command not working2024-02-16T15:03:31ZDBLouisargonaut-ldap2zone view command not workingThe following command does not work and print help instead :
argonaut-ldap2zone --verbose --ldap2view <view_name> <zone_name>The following command does not work and print help instead :
argonaut-ldap2zone --verbose --ldap2view <view_name> <zone_name>Argonaut 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/1014Argonaut should handle multi-server2024-02-16T15:03:17ZCôme ChillietArgonaut should handle multi-serverArgonaut should have a way to handle several servers, with attribution of PCs to servers.
The main question is to know how do we store in LDAP the relation PC<->ArgonautServer
The easiest way seems to have a field "argonautServer" in PC...Argonaut should have a way to handle several servers, with attribution of PCs to servers.
The main question is to know how do we store in LDAP the relation PC<->ArgonautServer
The easiest way seems to have a field "argonautServer" in PC or most probably group LDAP entry that contains the server dn.
The other question is do we handle in PHP the research for the right Argonaut server or do we send the request to a "master server" that then contact the right one.
It seems to me that it's more logical to handle this search in the PHP.Argonaut 1.4Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5702Removing a reverse zone in FD does not actually remove the configuration in t...2024-02-16T14:52:04ZjbecotRemoving a reverse zone in FD does not actually remove the configuration in the DNS master### Description
<!-- Required -->
Argonaut-ldap2zone does not remove configuration if we remove a reverse zone.
### Distribution Name and Version
<!-- Required -->
RHEL 7.3
### Argonaut Version
<!-- Required -->
1.2
### PERL versio...### Description
<!-- Required -->
Argonaut-ldap2zone does not remove configuration if we remove a reverse zone.
### Distribution Name and Version
<!-- Required -->
RHEL 7.3
### Argonaut Version
<!-- Required -->
1.2
### PERL version used
<!-- Required -->
v5.16.3
### Origin of perl packages
<!-- Required -->
Epel, Redhat channels (server-optionnal / server) and argonaut-libs
### Steps to Reproduce
<!-- Required -->
1. Create a reverse
2. Add records in that reverse
3. Update via argonaut
4. Delete the reverse
5. Update again with ldap2zone
**Expected behavior:**
At least cleaning /etc/named/named.conf.ldap2zone to not include the /etc/named/named.conf.ldap2zone.reverse file
Removing the corresponding file would be the less
Removing the refering zone file would be a plus (at least on the master side, because it is not handled by argonaut in the slave servers)
**Actual behavior:**
Neither the /etc/named/named.conf.ldap2zone file including /etc/named/named.conf.ldap2zone.reverse and the related file, nor the /var/named/db.reverse. zone file are deleted
The reverse lookup works while the forward may be inconsistent
**Reproduces how often:**
<!-- What percentage of the time does it reproduce?-->
100%
### Additional Information
<!-- optional -->
<!-- Any additional information, configuration or data that might be necessary to reproduce the issue. -->Argonaut 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5458Argonaut client silently dies when Argonaut-Server SSL CA is wrong using https2024-02-16T14:50:49ZjbecotArgonaut client silently dies when Argonaut-Server SSL CA is wrong using httpsHello,
Setup :
Argonaut-server configured with https.
Argonaut-server configured to use a registered certificate but the root CA does not include the intermediate certification chain.
Argonaut-client configured to use https.
Argonaut-c...Hello,
Setup :
Argonaut-server configured with https.
Argonaut-server configured to use a registered certificate but the root CA does not include the intermediate certification chain.
Argonaut-client configured to use https.
Argonaut-client configured to use a registered certficate, and its rootCA includes the intermediate certification chain.
Bug :
Launching a DNS Zone Refresh from FD gives a 500 error (expected). But argonaut-client silently fails and stops. No trace in the log file, no error displayed when launched with -X option.
Solution:
Using the same rootCA including the chain in argonaut-server config works fine.Argonaut 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/3548NET::LDAP does not follow referrals2024-02-16T14:49:44ZCôme ChillietNET::LDAP does not follow referralsArgonaut won’t work if contacting an LDAP referral.Argonaut won’t work if contacting an LDAP referral.Argonaut 1.4Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5780remove all leftover of opensides.be inside the sources2024-02-16T14:48:56Zbmortierremove all leftover of opensides.be inside the sourcesArgonaut 1.3.1bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/4629Better handling of timeouts2024-02-16T14:48:08ZCôme ChillietBetter handling of timeoutsIt seems argonaut client timeout is 10 in JSON::RPC::Client code and we can’t change it.
We should find a way to change this and make sure client timeout is always longer than server timeout.
Argonaut server state cache may be activated...It seems argonaut client timeout is 10 in JSON::RPC::Client code and we can’t change it.
We should find a way to change this and make sure client timeout is always longer than server timeout.
Argonaut server state cache may be activated again thanks to these changes (see #2426 )Argonaut 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5750Possibility to modify peer_name2024-02-16T14:47:45ZJonathan SwaelensPossibility to modify peer_name## Descriptive title for this enhancement
Possibility to modify peer_name
### Actual behavior
We need to use correct informations for ssl
### Expected behavior
Be able to use https with localhost and validation enabled
### Benefits...## Descriptive title for this enhancement
Possibility to modify peer_name
### Actual behavior
We need to use correct informations for ssl
### Expected behavior
Be able to use https with localhost and validation enabled
### Benefits
Keep the ssl validation enabledArgonaut 1.4Jonathan SwaelensJonathan Swaelenshttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5772add dmarc dns record support to the dns plugin2024-02-16T14:47:00Zbmortieradd dmarc dns record support to the dns plugin## Descriptive title for this enhancement
<!-- required -->
add dmarc dns record support to the dns plugin
### Actual behavior
<!-- What actually happens -->
we don't know if argonaut support correctly the dmarc dns record
### Expe...## Descriptive title for this enhancement
<!-- required -->
add dmarc dns record support to the dns plugin
### Actual behavior
<!-- What actually happens -->
we don't know if argonaut support correctly the dmarc dns record
### Expected behavior
<!-- What you expect to happen-->
to ba able to generated dmarc record from ldap for bind
### Benefits
<!-- optional -->
<!-- What benefits will be realized by the code change? -->
be able to manage dns records with FusionDirectory & argonaut-ldap2zone
### Possible Drawbacks
<!-- optional -->
<!-- What are the possible side-effects or negative impacts of the code change? -->
noneArgonaut 1.4bmortierbmortier2021-07-30https://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5766Argonaut find always 2 computers with same Mac / IP ( was : cannot use OPSI p...2024-02-16T14:45:29ZagallavardinArgonaut find always 2 computers with same Mac / IP ( was : cannot use OPSI plugins with argonaut server in order to setup OPSI profil)### Description
FD and argonaut server are installed from git and are successfully working with dns system.
I setup an opsi server listening without ssl on the correct port
When I tried to fetch opsi product I got the following error on...### Description
FD and argonaut server are installed from git and are successfully working with dns system.
I setup an opsi server listening without ssl on the correct port
When I tried to fetch opsi product I got the following error on argonaut-server.log
```
Nov 16 19:18:10 [NOTICE] Several computers matches (macAddress=08:00:27:72:da:55).
Nov 16 19:18:10 [INFO] sending action Argonaut.ClientDaemon.Modules.OPSI.get_netboots to 10.0.2.11
Nov 16 19:18:10 [ERROR] Error : No such a method : 'Argonaut.ClientDaemon.Modules.OPSI.get_netboots'.
2020/11/16 19:18:10 App::Daemon die handler triggered.
2020/11/16 19:18:10 Die handler called by eval. Ignored.
Nov 16 19:18:10 [DEBUG] Setting task error 'Error : No such a method : 'Argonaut.ClientDaemon.Modules.OPSI.get_netboots'.
' for task '0'
Nov 16 19:18:10 [DEBUG] deleting task
```
Server are setup with an network interface (mandatory for argonaut)
### Distribution Name and Version
Debian 10
### Argonaut Version
1.4-dev from git
### PERL version used
v5.28.1 from Debian 10
### Steps to Reproduce
1. Fusion is installed from Git
2. Argonaut is install from git (see [install-argonaut.txt](/uploads/ce7f44c64627c2885964ef44d5aae5fc/install-argonaut.txt))
3. opsi server is declared setup ( see [opsi-server.txt](/uploads/04bacb6f8f99e48a319c400838afd4fe/opsi-server.txt) to see the ldif )
**Expected behavior:**
I should be able to fetch all netboot and local producte from opsi server in order to create some software profile
**Actual behavior:**
Erreur occurs when trying tu communicate to the opsi server trough argonaut server
> Error : No such a method : 'Argonaut.ClientDaemon.Modules.OPSI.get_netboots
**Reproduces how often:**
100%
### Additional Information
After some search argonaut failed because it didn't only one computer with the correct Mac address, but 2 : the server himself and the network card assign to the server.
I tried to restrict trough ldap request to request only server ( see [argonau-common.pm.patch](/uploads/e72cb63486604399a597b0d7e823b104/argonau-common.pm.patch))
It seems to works, only one draw back : an error occurs when I try to "ping" aka check if host is alive with argonaut
```
Did not get DONE/CLOSE event for Wheel ID 11 from IP ::ffff:10.0.2.4 at /usr/share/perl5/POE/Component/Server/SimpleHTTP.pm line 226.
Cannot remove /var/run/argonaut/argonaut-server.pid at /usr/share/perl5/App/Daemon.pm line 212.
encountered object '1', but neither allow_blessed, convert_blessed nor allow_tags settings are enabled (or TO_JSON/FREEZE method missing) at /usr/share/perl5/POE/Component/Server/JSONRPC.pm line 223.
```
but I was able to restart start/stop service trough service tabs of the serverArgonaut 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/4510IPv6 support2024-02-16T14:40:29ZCôme ChillietIPv6 supportWe need to check if Argonaut server behaves correctly when only IPv6 are in use.
Deployment with FAI through FD should still work.We need to check if Argonaut server behaves correctly when only IPv6 are in use.
Deployment with FAI through FD should still work.Argonaut 1.4bmortierbmortier