fusiondirectory issueshttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues2023-03-09T16:52:55Zhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/5979Samba and FD2023-03-09T16:52:55ZbmortierSamba and FD* Samba 3 works well with Fd and an external LDAP tree . FD is obliged to maintain a dependency between Posix account and samba Account . OK no problem with it !
* Samba 4 contains is own LDAP directory . From several advice the best way...* Samba 3 works well with Fd and an external LDAP tree . FD is obliged to maintain a dependency between Posix account and samba Account . OK no problem with it !
* Samba 4 contains is own LDAP directory . From several advice the best ways is to create a task to sync internal SAMBA LDAP from FD Ldap with LSC ( for example)(by the way, you could replace Samba 4 per ActiveDirectory)
In the last case, Is it necessary to keep a dependency posix <=> samba tab ?
This dependency is constraining ...
In fact I just want to create an "Microsoft" Identity wich could be done without providing all posix field like uidNumber, Posixnumber home Directory and so one ..
A flag could be done in samba plugin config backend ? ( no idea about consequence , but I guess that is the same problem for group)
Available to discuss on It .FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6153Remove samba domain caching from core2021-07-29T19:46:21ZbmortierRemove samba domain caching from coreCaching samba domains information is now done in samba plugin.
Since this was the last one in config::load_servers this method can now safely be removed.Caching samba domains information is now done in samba plugin.
Since this was the last one in config::load_servers this method can now safely be removed.FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/5931Use date HTML5 input type for DateAttribute2021-01-29T20:49:02ZbmortierUse date HTML5 input type for DateAttributeFrom #5910
> The hard decision is whether to replace our date input by the type=date HTML5 input. Here is the support matrix: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date#Browser_compatibility
>
> All major bro...From #5910
> The hard decision is whether to replace our date input by the type=date HTML5 input. Here is the support matrix: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date#Browser_compatibility
>
> All major browsers seem to support it, and I expect most of them will have a better interface than our old fashion datepicker. It would mean switching from d.m.Y to YYYY-MM-DD format for POST value. We may keep d.m.Y as internal value to avoid confusing webservice and internal code (but I do think YYYY-MM-DD is a better and more widely used format).
>
> For outdated browser, they would in this case show a text input field and users would have to "guess" they need to enter YYYY-MM-DD format. We can detect this case in javascript and maybe add a text to explain this, or even try to add the old datepicker (but that means adapt its code to support YYYY-MM-DD format). We can use pattern attribute to force NNNN-NN-NN format (with N an integer), which is more widely supported (IE>=10).
I think we should migrate DateAttribute to HTML5 and to `YYYY-MM-DD` internal format. It may break external tools relying on the webservice.
It could break some internal features but this seems unlikely.
I think we should drop the JS datepicker entirely.
This should be done in a major release, so either %"FusionDirectory 1.4" or 1.5.FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/1727the management of the windows workstations in the samba plugin should be migr...2019-01-24T17:31:27Zbmortierthe management of the windows workstations in the samba plugin should be migrated to simple pluginHello,
we need to migrate the windows workstations management to simple plugin. This need to be done to be able to make the opsi plugin after
Cheers
*(from redmine: issue id 1727, created on 2013-01-09, closed on 2013-01-17)*
* Chang...Hello,
we need to migrate the windows workstations management to simple plugin. This need to be done to be able to make the opsi plugin after
Cheers
*(from redmine: issue id 1727, created on 2013-01-09, closed on 2013-01-17)*
* Changesets:
* Revision 22b2145469a6d84f09d7b1a4f295556bae845eea by Côme Chilliet on 2013-01-09T16:37:25.000Z:
```
Fixes: #1727 the management of the windows workstations in the samba plugin should be migrated to simple plugin
```
* Custom Fields:
* Bug in version: 1.0.5
* Uploads:
* [0001-Fixes-1727-the-management-of-the-windows-workstation.patch](/uploads/fabe99e33438a2313e47b27f33d717b4/0001-Fixes-1727-the-management-of-the-windows-workstation.patch)FusionDirectory 1.0.5bmortierbmortier